System and method for composing, processing, and organizing electronic mail message items

ABSTRACT

In an electronic mail system environment, a system and method for automatically checking recipients&#39; names, providing message flags, providing custom forms, and providing an autoresponse feature. Recipients&#39; names are resolved in the background, while the user of the e-mail system is composing the message. The user easily resolves ambiguous names by using a context menu. The resolved ambiguous names are automatically used to create nicknames, which are used to resolve ambiguous names in the future. Message flags allow a sender or recipient to identify required follow-up action and a deadline. The recipient may use the message flags to quickly determine which messages require follow-up action. The e-mail system notifies a recipient when a due date is approaching or when a follow-up action is past due. A custom forms feature allows a user to create and share custom forms without requiring the form to be published or installed by other user. The custom form&#39;s attributes are transmitted to the recipient as an element of the e-mail message. An autoresponse feature allows a sender to create a message that includes voting buttons corresponding to the possible responses to a query. A recipient replies by selecting one of the voting buttons. The recipient&#39;s vote is automatically tallied in the sender&#39;s copy of the message, thus allowing the sender to view a vote tally, a list of the recipients, and their response.

TECHNICAL FIELD

[0001] The present invention relates to a system and method for creatingand sending electronic mail, and more particularly relates to a systemand method for simplifying the processes of resolving recipient names,indicating action items, utilizing custom forms, and tallying repliesfrom a group of recipients.

BACKGROUND OF THE INVENTION

[0002] Electronic mail, or e-mail, is a service that transmitselectronic messages from one computer to another. These messages may besimple text messages or more complex messages containing documents anddata of various types. The transmission of e-mail messages may rangefrom transmission over a short distance, such as over a local areanetwork between employees in adjoining offices, to transmission overextremely long distances, such as over the global Internet between userson different continents.

[0003] Generally, to send an e-mail message via an e-mail system, a useropens an e-mail program module and types a message and other informationinto an e-mail form. The e-mail form contains a number of fields for therecipients' addresses, the subject of the message, and the messageitself. The user may also attach separate files to the e-mail message.Before sending the e-mail message, the user must enter the recipient'se-mail address, which is used by the e-mail system to route the messageto the intended recipient.

[0004] After composing an e-mail message and entering the recipient'saddress, the user sends the message by invoking a “send” command. Thee-mail system then sends the message to the recipient. At therecipient's computer, the recipient typically will receive a visual orauditory cue, such as a ringing bell, when an e-mail message has beenreceived in the recipient's inbox. The recipient may then open thee-mail program and view a list of the messages in the inbox. Therecipient may view the complete text of a message by selecting andopening that message.

[0005] E-mail is becoming increasingly popular because it is a quick,convenient, and easy way to exchange information and communicate withothers. E-mail offers numerous advantages over other forms ofcommunication. For example, e-mail is less intrusive than a telephonecall because the recipient of an e-mail message may wait until aconvenient time to retrieve and respond to the message rather than beingimmediately interrupted. Another advantage of e-mail is the ability tocommunicate with large groups of people by sending a single e-mailmessage to multiple recipients. Still another advantage of e-mail is theability of attaching documents in electronic format to an e-mailmessage.

[0006] E-mail messages are composed in the context of a “form.” A formis an object that is used to display a message in a structured format.An e-mail form typically provides a plurality of fields, including anaddress field, a “From” field, a “Subject” field, a “cc” field, and a“Body” field. The user of the e-mail system composes the message byentering data into some or all of the fields on the form.

[0007] E-mail forms typically incorporate verbs, which are commands thata form is capable of executing. Typical verbs include commands such asreply, forward, open, and print. For example, a recipient may generate areply to an e-mail message by clicking on a reply button. In response tothe reply command, the e-mail program carries out the instructionsassociated with the “reply” verb. This includes copying the data in theaddress field of the incoming message to the “From” field of the reply,copying the data in the “From” field of the incoming message to theaddress field of the reply, and adding “Re:” before the data in the“Subject” field.

[0008] Although e-mail provides a valuable and useful tool, currente-mail systems are not without their drawbacks. For instance, an e-mailsystem must have a unique, specific destination address in order todeliver an e-mail message to the correct recipient. In many cases,e-mail addresses are not intuitive derivatives of a person's name andmay be difficult for the user to remember. Also, because the addressmust be specific, a typographical error entered by the user will resultin the message being misdelivered or not delivered at all.

[0009] Before the e-mail system can send a message, all of the names inthe address field must be “resolved,” or matched with the valid addressof a particular user. In most e-mail systems, the recipients' names areresolved when the user invokes the “send” command or a “check names”command. In either case, the e-mail system resolves unambiguous nameswithout user intervention and prompts the user to resolve ambiguousnames by selecting the correct name from a short list.

[0010] As an example, Jim Peterson is sending an e-mail message to hisfriend Dave. In the address field of the message, Jim enters the name“Dave.” An address book or directory, which is stored on the server, isused by the e-mail system to match the name “Dave” with the appropriaterecipient. In a small company or organization with only one user namedDave, entering “Dave” in the address field would be unambiguous to thee-mail system and the e-mail system would match the name “Dave” to thecorrect, unique e-mail address. However, in a company or organizationwith multiple Daves, the name must be resolved to the correct Dave. Thismethod of resolving names is inconvenient because the user must executean extra step to resolve the names before the message is sent. This isespecially inconvenient if a user only sends mail to one “Dave” althoughthe address book contains many “Daves.” Also, as companies andorganizations expand, the e-mail system address book continues to grow,thereby increasing the chances for ambiguity. The potential is createdfor false matches resulting in misdirected e-mail.

[0011] One attempt to simplify the process of resolving names is toimplement a feature that monitors the user's typing of characters in theaddress field and volunteers the full name when the user types enoughcharacters to uniquely identify one recipient. Alternatively, in anotherattempted solution, the user can type in a number of characters and geta list of recipients whose name begins with the characters typed in bythe user. Neither of these solutions provides a satisfactory solution tothe problem of resolving names. First, a long string of characters mayneed to be entered before a unique name is found. Also, for certainnames, such as John Smith, a unique name may never be found even if theentire name is entered. In addition, the user must enter the nameexactly as it appears in the directory even if one part of a name ismore unique than another part of a name. For example, “MacDonald” isprobably more unique than “John,” but a user must enter the name as“John Mac . . . ” if that is how the name appears in the directory.Furthermore, these attempted solutions require the user's attention tocomplete the resolution of the names.

[0012] In addition to the drawbacks associated with verifying e-mailaddresses, current e-mail systems do not provide the user with aneffective way to organize and manage the user's e-mail inbox. Manybusinesses rely on an e-mail system as one of the main modes ofcommunication between individuals, resulting in users often having todeal with large numbers of e-mail messages. In cases where an e-mailuser has received messages that delegate responsibilities or requestspecific follow-up actions, these messages may easily be lost in a floodof other e-mail messages. Even if a recipient has a manageable amount ofe-mail messages in his or her inbox, requests for action are oftenburied in the body of an e-mail message and the recipient may notrealize that an action has been requested.

[0013] E-mail systems usually provide only rudimentary mechanisms foridentifying and sorting important messages that require some sort ofaction. For example, one mechanism for identifying and sorting importantmessages is for the sender of the message to set a priority for themessage that the recipient will receive with the message. In thealternative, the sender may provide information about the e-mail messagein the subject line. For example, the sender may set the priority as“urgent” for a respective e-mail message or type “urgent” in the“Subject” field. However, this mechanism of setting priorities isineffective because the e-mail message may not require immediate action.The recipient may open and read the message, and then file the messagein a “follow-up” folder. Thus, there is the possibility that therecipient will forget to take the action at a later time.

[0014] Another mechanism for identifying and sorting important messagesis for the recipient of the message to forward the message to himselfand change the priority of the message or subject of the message to thepriority or subject desired by the recipient. However, re-prioritizingby the recipient suffers from the drawback of the recipient spendingextra time and effort to execute the steps of sending a message back tohimself. Thus, the previous solutions to organize and identify importante-mail messages, such as those that require action, only achieveadequate results at best.

[0015] Another drawback of current e-mail systems is the difficulty increating and using customized e-mail forms. There are times when a userfeels that the fields on an e-mail form simply do not meet theirrequirements and that it would be useful to add user-specified fields.For example, Jim is working with Shirley to develop a casing for theradio she is designing. E-mail messages containing information about thedimensions of the radio are constantly being sent between the two. Usinga normal e-mail message, the information is buried within the messagemaking it difficult to find. As a result, Jim and Shirley would like tocreate a customized e-mail form with added fields for the length, width,and height of the casing.

[0016] Currently, to add fields to an e-mail message, a custom form iscreated using a separate application program. After the form is createdand defined, the form must be placed on a central server fordistribution and installed in each user's form registry. Usually,placing the form on the server must be approved and executed by themanagement information systems (MIS) department. Thus, placing a form ona server may involve some delay and bureaucratic problems After the formis placed on the server, any user of the form must install the formbefore an e-mail message using this form may be displayed on theirscreen. For instance, in the above example, Jim would have to installthe form on his computer before receiving an e-mail message from Shirleyutilizing the form. Therefore, using a form with user-specified fieldsmay be time-consuming and annoying because the form must be created andplaced on a server, and the form must be installed on a user's computerbefore the form can be used.

[0017] Another drawback of current e-mail systems is an inability toeffectively organize responses to an e-mail message from a group ofpeople. For example, when working with a large group, a user is oftenrequired to interact with other group members to make decisions. Usingan e-mail message to pose a question to a large group reduces thedifficulty of contacting each member of the group for their response.Instead of directly contacting each member of the group, one e-mailmessage requesting a response can be sent to every member of the group.Each recipient types in their response and sends a reply e-mail messageto the user. However, the user still has the task of organizing thereplies as they are received and tallying the responses to determine thegroup consensus. Thus, the user is required to open every reply, read itto determine the response, and tally the responses to decide theconsensus of the group. Current e-mail systems do not provide amechanism for automatically tallying the responses to a question.Instead, the user must manually organize the responses, typically bycreating folders for each of the different responses, by creating aspreadsheet with the different responses and the number of repliesassociated with each response, or simply by tracking the responses onpaper. However, these solutions require time and effort on the part ofthe user and do not directly address the issue of tallying responses.

[0018] Therefore, there is a need in the art for an e-mail system thatis easier to use and provides more useful organizational features thancurrent e-mail systems.

[0019] In particular, there is a need for an e-mail system thatsimplifies the process of resolving recipient addresses and minimizesthe input required from the user.

[0020] There is also a need for an e-mail system that provides moreuseful organizational features for the recipient by distinctlyidentifying important e-mail messages, such as messages that requirefollow-up action.

[0021] There is a further need for an e-mail system that provides theability to use custom forms with user-specified fields without requiringthe forms to be created and stored on a server.

[0022] There is still a further need for an e-mail system that providesmore useful organizational features by automatically tallying theresponses to a question posed to a group of e-mail users.

SUMMARY OF THE INVENTION

[0023] The present invention satisfies the above described needs byproviding an improved system and method for composing, processing, andorganizing electronic mail message items. The present inventionautomatically resolves recipient display names while the user iscomposing the message. The invention provides multiple options forresolving ambiguous names and automatically creates nicknames based onhow ambiguous names are resolved. The present invention also allows asender or recipient to indicate specific follow-up action associatedwith a message. The message flag may be accompanied by a due date, whichgenerates reminders and past due notices. The present invention alsoprovides an efficient method for sharing custom e-mail forms with otherusers. A description of the custom form is transmitted as part of thee-mail message and displayed by the recipient's computer. The presentinvention also automatically tallies multiple responses to a query. Thesender sends a message that includes a query and specific choices forthe response. The recipient creates a reply by selecting one of thepredefined choices. When the original sender receives the reply, thesent mail copy of the message is updated to tally the votes.

[0024] Generally described, in one aspect, the present inventionprovides a method for resolving a display name associated with anintended recipient of a message item, which is sent in the context of anelectronic mail system. The method includes receiving the display namein an address field and determining whether the display name uniquelymatches one of a plurality of registered users of the electronic mailsystem. If the entered address data uniquely matches one of theregistered users, data corresponding to the matching registered user isdisplayed. Otherwise, ambiguous address data is displayed.

[0025] More particularly described, the present invention provides amethod for using nicknames to resolve the name of an intended recipientof a message item. The method includes receiving a display name in anaddress field and determining whether the display name corresponds to apreviously stored nickname. If so, nickname data corresponding to aregistered user associated with the nickname is displayed. If nonickname is found, the method determines whether the display nameuniquely matches one of a plurality of registered users of theelectronic mail system. If so, recipient data corresponding to thematching registered user is displayed. If there is no unique match, theambiguous address data is displayed.

[0026] In another aspect, the present invention provides a method forincluding a flag with the message item, which is transmitted in anelectronic mail system. Flag data is received and stored as one of aplurality of message properties. The e-mail message item is thentransmitted to a recipient.

[0027] The message item can also include a combination of a due dateproperty and the message flag property. The computer receives due datedata indicative of a date by which the follow-up action is to beperformed and stores the due date data as one of the plurality ofproperties.

[0028] The present invention also provides a method for displaying thestatus of a follow-up action associated with the message item. Themethod includes receiving a message item that includes a status propertyassociated with the follow-up action and determining whether the messageitem includes the status property. If so, the data associated with thestatus property is received and is displayed in conjunction with themessage item.

[0029] More particularly described, the present invention provides animproved message item for transmission in an electronic mail system. Themessage item includes a message flag property and a status property. Themessage flag property is indicative of a follow-up action associatedwith the message item. The status property includes status dataindicative of whether the follow-up action has been completed by arecipient of the message item.

[0030] In yet another aspect, the present invention provides a methodfor transmitting custom form data as part of a message item. Custom formdata is obtained. The custom form data indicates the layout of a customform comprising a plurality of fields for displaying field data. Thecustom form data is stored as one of a plurality of propertiesassociated with the message item. Once the message is composed, themessage item, including the form property, is transmitted to therecipient.

[0031] The present invention also provides a method for receiving amessage item that includes custom form data and displaying the messageitem in a custom form. A message item, which includes a plurality ofproperties, is received. The method includes determining whether themessage item includes a form property. If the message item includes aform property, the custom form data that is stored in the form propertyis retrieved and the message is displayed in the context of thecorresponding form. If the message item does not include a formproperty, standard form data is retrieved from a form registry and themessage item is displayed in the context of the standard form.

[0032] In yet another aspect, the present invention provides a methodfor sending a message item to a plurality of recipients andautomatically tallying the responses. A message item is created, andincludes a query and a plurality of predefined responses. The message istransmitted to the recipients. When a reply is received, the responseincluded in the reply is automatically tallied.

[0033] The original message item can include an autoresponse property.If so, response data corresponding to the predefined responses isreceived from the sender of the message item. The response data is thenstored in the autoresponse property. Responses are tallied by readingidentification data in the reply message and locating a sent mail copyof the original message. A voter property is located in the sent mailcopy and the reply data is stored in the voter property of the sent mailcopy.

[0034] More particularly described, the present invention provides amethod for selecting one of a plurality of predefined responses in replyto a message item that includes a query. A message is opened and aplurality of voting buttons is displayed. Each voting button correspondsto one of the predefined responses. Input corresponding to the selectionof one of the voting buttons is received and a reply message item iscreated. Data corresponding to the selected voting button is stored inone of the properties of the reply message.

[0035] It is therefore an object of the present invention to provide amethod for resolving recipient names in the background.

[0036] It is a further object of the present invention to simplify theprocess of resolving ambiguous names and to automatically createnicknames based on how the ambiguous names are resolved.

[0037] It is a further object of the present invention to provide amethod for specifying a follow-up action and due date associated with amessage item.

[0038] It is a further object of the present invention to assist theuser in managing e-mail messages that include specific follow-upactions.

[0039] It is a further object of the present invention to allow e-mailusers to create custom e-mail forms and easily share the custom formswith other users.

[0040] It is a further object of the present invention to provide amethod for soliciting input from a group of e-mail recipients andautomatically tallying their responses.

[0041] These and other objects, features, and advantages of the presentinvention may be more clearly understood and appreciated from a reviewof the following detailed description of the disclosed embodiments andby reference to the appended drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0042]FIG. 1 is a block diagram of a personal computer that provides theoperating environment for the preferred embodiment of the presentinvention.

[0043]FIG. 2 is a block diagram illustrating the interface between acomputer's input/output devices, an operating system, and an applicationprogram.

[0044]FIG. 3 is a diagram illustrating the modular architecture definedby the Messaging Application Programming Interface (MAPI).

[0045]FIG. 4 is a diagram illustrating the hierarchical arrangement of aMAPI message store.

[0046]FIG. 5 is a diagram illustrating the MAPI form architecture.

[0047]FIG. 6, consisting of FIGS. 6a-c, illustrates the principal userinterface provided by an automatic name checking feature of thepreferred embodiment of the present invention.

[0048]FIG. 7, consisting of FIGS. 7a-c, illustrates the user interfaceassociated with the process of resolving nicknames in accordance withthe preferred embodiment of the present invention.

[0049]FIG. 8 is a flow diagram illustrating the preferred method forresolving e-mail addresses, as performed by the user.

[0050]FIG. 9 is a flow diagram illustrating the preferred method forresolving e-mail addresses, as performed by the computer.

[0051]FIG. 10 is a state diagram illustrating the preferred method forresolving nicknames, as performed by the computer.

[0052]FIG. 11 is a diagram illustrating the data properties thatconstitute an e-mail message item including a message flag.

[0053]FIG. 12 is a flow diagram illustrating the preferred method foradding a message flag to an e-mail message, as performed by a user.

[0054]FIG. 13 is a state diagram illustrating the preferred method foradding a message flag to an e-mail item, as performed by a computer.

[0055]FIG. 14 is an illustration of a screen display containing a listview of the messages in a user's inbox in accordance with the preferredembodiment of the present invention.

[0056]FIG. 15 is an illustration of a screen display of a message viewof an e-mail message including a message flag in accordance with thepreferred embodiment of the present invention.

[0057]FIG. 16 is a flow diagram illustrating the preferred method forreviewing and editing an e-mail message, as performed by the user.

[0058]FIG. 17 is a state diagram illustrating the preferred method forreviewing and editing an e-mail message, as performed by a computer.

[0059]FIG. 18 is a flow diagram illustrating the preferred method forgenerating reminders and past due indicia associated with e-mailmessages that include message flags.

[0060]FIG. 19 is a diagram illustrating the data properties thatconstitute an e-mail item that uses a custom form in accordance with thepreferred embodiment of the present invention.

[0061]FIG. 20 is a flow diagram illustrating the preferred method forcreating and sending an e-mail message that uses a custom form, asperformed by a user.

[0062]FIG. 21 is an illustration of a field chooser dialog box inaccordance with the preferred embodiment of the present invention.

[0063]FIG. 22 is a state diagram illustrating the preferred method forcreating and sending an e-mail message that uses a custom form, asperformed by the computer.

[0064]FIG. 23 is an example of a screen display that is displayed to thesender of an e-mail message that uses a custom form in accordance withthe preferred embodiment of the present invention.

[0065]FIG. 24 is a flow diagram illustrating the preferred method forreceiving and displaying an e-mail message with a custom form, asperformed by the computer.

[0066]FIG. 25 is a representative example of a screen display of a“read” page that is displayed to the recipient of an e-mail message thatuses a custom form.

[0067]FIG. 26 is a diagram illustrating the data properties thatconstitute an autoresponse e-mail message item in accordance with thepreferred embodiment of the present invention.

[0068]FIG. 27 is a flow diagram illustrating the preferred method forcreating and sending an autoresponse message, as performed by a user.

[0069]FIG. 28 is an illustration of a screen display of an options pagefor selecting an autoresponse message.

[0070]FIG. 29 is a state diagram illustrating the preferred method forcreating and sending an autoresponse message, as performed by thecomputer.

[0071]FIG. 30 is a flow diagram of the steps performed in replying to anautoresponse message, as performed by a user.

[0072]FIG. 31 is a representative example of a screen display of arecipient's view of an autoresponse message.

[0073]FIG. 32 is a state diagram illustrating the preferred method foropening an autoresponse message and sending a reply to an autoresponsemessage, as performed by the computer.

[0074]FIG. 33 is a flow diagram illustrating the steps carried out inthe background to process an autoresponse reply message.

[0075]FIG. 34 is a state diagram illustrating the preferred method forupdating the sent mail copy of an autoresponse message, as performed bythe computer.

[0076]FIG. 35 is an example of a screen display of an inbox of thesender of an autoresponse message in accordance with the preferredembodiment of the present invention.

[0077]FIG. 36 is an example of a screen display of the sent mail copy ofan autoresponse message in accordance with the preferred embodiment ofthe present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0078] The present invention is directed to features associated with anelectronic mail (e-mail) program module. The preferred embodiment of thepresent invention is represented by the “MICROSOFT OUTLOOK” program,which is a workgroup personal information management program publishedby Microsoft Corporation of Redmond, Washington. Briefly described, thepreferred program allows users to manage their own calendar, messages,tasks, notes, and contacts and to share this information with others.Like many personal information managers, the preferred applicationprogram is divided into several modules, including a calendar manager, atask list manager, a contact manager, a message manager (e-mail), and anotes manager.

[0079] Although the preferred embodiment will be generally described inthe context of a program and an operating system running on a personalcomputer, those skilled in the art will recognize that the presentinvention also can be implemented in conjunction with other programmodules for other types of computers. Furthermore, those skilled in theart will recognize that the present invention may be implemented in astand-alone or in a distributed computing environment. In a distributedcomputing environment, program modules may be physically located indifferent local and remote memory storage devices. Execution of theprogram modules may occur locally in a stand-alone manner or remotely ina client/server manner. Examples of such distributed computingenvironments include local area networks of an office, enterprise-widecomputer networks, and the global Internet.

[0080] The detailed description which follows is represented largely interms of processes and symbolic representations of operations byconventional computer components, including a central processing unit(CPU), memory storage devices for the CPU, display devices, and inputdevices. Furthermore, these processes and operations may utilizeconventional computer components in a heterogeneous distributedcomputing environment, including remote file servers, remote computeservers, and remote memory storage devices. Each of these conventionaldistributed computing components is accessible by the CPU via acommunications network.

[0081] The processes and operations performed by the computer includethe manipulation of signals by a CPU or remote server and themaintenance of these signals within data structures resident in one ormore of the local or remote memory storage devices. Such data structuresimpose a physical organization upon the collection of data stored withina memory storage device and represent specific electrical or magneticelements. These symbolic representations are the means used by thoseskilled in the art of computer programming and computer construction tomost effectively convey teachings and discoveries to others skilled inthe art.

[0082] For the purposes of this discussion, a process is generallyconceived to be a sequence of computer-executed steps leading to adesired result. These steps generally require physical manipulations ofphysical quantities. Usually, though not necessarily, these quantitiestake the form of electrical, magnetic, or optical signals capable ofbeing stored, transferred, combined, compared, or otherwise manipulated.It is conventional for those skilled in the art to refer to thesesignals as bits, bytes, words, data, objects, properties, flags, types,identifiers, values, elements, symbols, characters, terms, numbers,points, records, images, files or the like. It should be kept in mind,however, that these and similar terms should be associated withappropriate physical quantities for computer operations, and that theseterms are merely conventional labels applied to physical quantities thatexist within and during operation of the computer.

[0083] It should also be understood that manipulations within thecomputer are often referred to in terms such as adding, comparing,receiving, sending, transmitting, replying, etc. which are oftenassociated with manual operations performed by a human operator. Theoperations described herein are machine operations performed inconjunction with various input provided by a human operator or user thatinteracts with the computer.

[0084] In addition, it should be understood that the programs,processes, methods, etc. described herein are not related or limited toany particular computer or apparatus, nor are they related or limited toany particular communication network architecture. Rather, various typesof general purpose machines may be used with program modules constructedin accordance with the teachings described herein. Similarly, it mayprove advantageous to construct a specialized apparatus to perform themethod steps described herein by way of dedicated computer systems in aspecific network architecture with hard-wired logic or programs storedin nonvolatile memory, such as read only memory.

[0085] Referring now to the drawings, in which like numerals representlike elements throughout the several figures, aspects of the presentinvention and the preferred operating environment will be described.

[0086] The Operating Environment

[0087] FIGS. 1-5 illustrate various aspects of the preferred computingenvironment in which the present invention is designed to operate. Thoseskilled in the art will immediately appreciate that FIGS. 1-5 and theassociated discussion are intended to provide a brief, generaldescription of the preferred computer hardware and program modules, andthat additional information is readily available in the appropriateprogramming manuals, user's guides, and similar publications.

[0088] The Computer Hardware

[0089]FIG. 1 illustrates a conventional personal computer 10 suitablefor supporting the operation of the preferred embodiment of the presentinvention. As shown in FIG. 1, the personal computer 10 operates in anetworked environment with logical connections to a remote computer 11.The logical connections between the personal computer 10 and the remotecomputer 11 are represented by a local area network 12 and a wide areanetwork 13. Those of ordinary skill in the art will recognize that inthis client/server configuration, the remote computer 11 may function asa file server or compute server.

[0090] The personal computer 10 includes a central processing unit (CPU)14, such as the 80486 or “PENTIUM” microprocessors manufactured by IntelCorporation of Santa Clara, Calif. The personal computer also includessystem memory 15 (including read only memory (ROM) 16 and random accessmemory (RAM) 17), which is connected to the CPU 14 by a system bus 18.The preferred computer 10 utilizes a BIOS 19, which is stored in ROM 16.Those skilled in the art will recognize that the BIOS 19 is a set ofbasic routines that helps to transfer information between elementswithin the personal computer 10. Those skilled in the art will alsoappreciate that the present invention may be implemented on computershaving other architectures, such as computers that do not use a BIOS,and those that utilize other microprocessors, such as the “MIPS” or“POWER PC” families of microprocessors from Silicon Graphics andMotorola, respectively.

[0091] Within the personal computer 10, a local hard disk drive 20 isconnected to the system bus 18 via a hard disk drive interface 21. Afloppy disk drive 22, which is used to read or write a floppy disk 23,is connected to the system bus 18 via a floppy disk drive interface 24.A CD-ROM drive 25, which is used to read a CD-ROM disk 26, is connectedto the system bus 18 via a CD-ROM interface 27. A user enters commandsand information into the personal computer 10 by using input devices,such as a keyboard 28 and/or pointing device, such as a mouse 29, whichare connected to the system bus 18 via a serial port interface 30. Othertypes of pointing devices (not shown in FIG. 1) include track pads,track balls, pens, head trackers, data gloves and other devices suitablefor positioning a cursor on a computer monitor 31. The monitor 31 orother kind of display device is connected to the system bus 18 via avideo adapter 32.

[0092] The remote computer 11 in this networked environment is connectedto a remote memory storage device 33. This remote memory storage device33 is typically a large capacity device such as a hard disk drive,CD-ROM drive, magneto-optical drive or the like. The personal computer10 is connected to the remote computer 11 by a network interface 34,which is used to communicate over the local area network 12.

[0093] As shown in FIG. 1, the personal computer 10 is also connected tothe remote computer 11 by a modem 35, which is used to communicate overthe wide area network 13, such as the Internet. The modem 35 isconnected to the system bus 18 via the serial port interface 30. Themodem 35 also can be connected to the public switched telephone network(PSTN) or community antenna television (CATV) network. Althoughillustrated in FIG. 1 as external to the personal computer 10, those ofordinary skill in the art will quickly recognize that the modem 35 mayalso be internal to the personal computer 11, thus communicatingdirectly via the system bus 18. It is important to note that connectionto the remote computer 11 via both the local area network 12 and thewide area network 13 is not required, but merely illustrates alternativemethods of providing a communication path between the personal computer10 and the remote computer 11.

[0094] Although other internal components of the personal computer 10are not shown, those of ordinary skill in the art will appreciate thatsuch components and the interconnection between them are well known.Accordingly, additional details concerning the internal construction ofthe personal computer 10 need not be disclosed in connection with thepresent invention.

[0095] Those skilled in the art will understand that program modulessuch as an operating system 36, application programs 37, and data areprovided to the personal computer 10 via computer-readable media. In thepreferred computer, the computer-readable media include the local orremote memory storage devices, which may include the local hard diskdrive 20, floppy disk 23, CD-ROM 26, RAM 17, ROM 16, and the remotememory storage device 33. In the preferred personal computer 10, thelocal hard disk drive 20 is used to store data and programs, includingthe operating system and programs.

[0096] The Operating System

[0097]FIG. 2 is a simplified block diagram illustrating the interactionbetween the computer hardware 200, the preferred operating system 36,and an application program 37a. Referring now to both FIGS. 1 and 2,when the personal computer 10 is turned on or reset, the BasicInput/Output System (BIOS) 19, which is stored in the ROM 16, instructsthe CPU 14 to load the operating system 36 from the hard disk drive 20into the RAM 17. Once the operating system 36 is loaded into RAM 17, theCPU 14 executes the operating system 36 and causes the visual elementsassociated with the user interface of the operating system 36 to bedisplayed on the monitor 31.

[0098] The operating system 36, in conjunction with the BIOS 19 (FIG. 1)and associated device drivers, provides the basic interface between thecomputer's resources, the user, and the application program 37 a. Theoperating system 36 interprets and carries out instructions issued bythe user. For example, when the user wants to load an applicationprogram 37 a, the operating system 36 interprets the instruction (e.g.,double clicking on the application program's icon) and causes the CPU 14to load the program code into RAM 17 from either the local hard diskdrive 20, floppy disk 23, CD-ROM 26, or the remote memory storage device33. Once the application program 37 a is loaded into the RAM 17, it isexecuted by the CPU 14. In case of large programs, the CPU 14 loadsvarious portions of program modules into RAM 17 as needed.

[0099] As discussed earlier, the preferred embodiment of the presentinvention is embodied in the “MICROSOFT OUTLOOK” program, which isdesigned to operate in conjunction with Microsoft Corporation's “WINDOWS95” or “WINDOWS NT” operating systems. However, it should be understoodthat the invention can readily be implemented in other operatingsystems, such as Microsoft Corporation's “WINDOWS 3.1” operating system,IBM Corporation's “OS/2” operating system, and the operating system usedin “MACINTOSH” computers manufactured by Apple Computer, Inc.

[0100] The operating system 36 provides a variety of functions orservices that allow an application program 37 a to easily deal withvarious types of input/output (I/O). This allows the application program37 a to issue relatively simple function calls that cause the operatingsystem 36 to perform the steps required to accomplish various tasks,such as displaying text on the monitor 31 (FIG. 1) or printing text onan attached printer (not shown). Generally described (with reference toFIG. 2), the application program 37 a communicates with the operatingsystem 36 by calling predefined functions provided by the operatingsystem 36. The operating system 36 responds by providing the requestedinformation in a message or by executing the requested task.

[0101] From this brief description, it should be appreciated thatoperating systems, such as the “WINDOWS 95” and “WINDOWS NT” operatingsystem, are quite complex and provide a wide variety of services thatallow users and programs to utilize the resources available in thepersonal computer. Those skilled in the art will be familiar withoperating systems and their various features, which include, but are inno means limited to, the specific messages and functions describedabove. For more comprehensive information regarding the “WINDOWS 95” and“WINDOWS NT” operating system and its interaction with programs, thereader may refer to any of a variety of publications, including the“Win32 Programmer's Reference” published by Microsoft Press and“Advanced Windows” published by Microsoft Press.

[0102] The MAPI Messaging Architecture

[0103] In the context of the present invention, the primary interactionbetween the preferred program and the operating system involvesmessaging related tasks. The preferred operating system incorporates theMessaging Application Programming Interface (MAPI). The MAPIarchitecture is designed to make it easy for programmers to writemessaging-enabled applications that are independent of the underlyingmessaging system. MAPI provides high-level function that can be used toimplement sophisticated messaging features with a relatively smallamount of code. The code deals only with functions for sending,receiving, and addressing messages. The underlying messaging system iscompletely transparent. MAPI also provides other message-relatedfunctionality, such as access to address books.

[0104]FIG. 3 illustrates the modular architecture defined by MAPI. Theclient applications 300 are application programs that take advantage ofthe MAPI subsystem 305. Client applications 300 implement messagingtasks as either their primary or secondary focus. Messaging-based clientapplications, such as applications that send and receive electronicmail, implement messaging tasks as their primary focus. Fornon-messaging client applications, which are referred to as being“messaging-enabled” or “messaging-aware,” it is a secondary feature.

[0105] The MAPI subsystem is made up of the MAPI spooler 310, a commonuser interface (not shown), and the programming interfaces 315. The MAPIspooler is a separate interface that is responsible for sending messagesto and receiving messages from a messaging system. The common userinterface is a set of dialog boxes that gives client applications aconsistent look and users a consistent way to perform tasks.

[0106] The programming interfaces 315 are used by the MAPI subsystem305, by client applications 300, and by service provider writers. Themain programming interface is an object-based interface known as theMAPI programming interface, which is based on the OLE Component ObjectModel. Client applications may also utilize any of three otherinterfaces, including simple MAPI, Common Messaging Calls (CMC) and theOLE Messaging Library, which are primarily for messaging-enabled andmessaging-aware client applications.

[0107] The MAPI spooler 310 is a separate process within the MAPIsubsystem 305 and is responsible for sending messages to and receivingmessage from a messaging system 320. The spooler runs as a backgroundprocess and also performs several functions related to messagingdistribution. These include informing a client application when a newmessage has been delivered, invoking message preprocessing and postprocessing, generating reports that indicate that message delivery hasoccurred, and maintaining status on processed recipients.

[0108] The MAPI service providers 325 are located between MAPI subsystem305 and the messaging systems 320. Service providers are drivers thatconnect MAPI client applications 300 to an underlying messaging system320. Most messaging systems include three types of service providers:message store providers 330, address book or directory providers 335,and message transport providers 340. The service providers work withMAPI to create and send messages in the following way. Messages arecreated using a form that is appropriate for the specific type, orclass, of message. The completed message is addressed to one or morerecipients. When the client sends the message, the message storeprovider 330 checks that each recipient has a unique and valid addressand that the message has all of the information necessary fortransmission. If there is a question about a recipient, such as canoccur when there are multiple recipients with the same name, an addressbook provider resolves the ambiguity. The message in then placed in theoutbound queue.

[0109] Address book providers 335 handle access to directoryinformation. Depending on the type of recipient and the address bookprovider, there is a wide range of information that can be madeavailable. For example, all address book providers 335 store arecipient's name, address, and address type and organize the data usingone or more containers. MAPI integrates all the information supplied bythe installed address book providers into a single address book, therebypresenting a unified view to the client application. The users of clientapplications can view the contents of address book containers and insome cases modify it. MAPI's Personal Address Book is an example of amodifiable address book container that allows new entries to be addedand exiting entries to be modified or deleted.

[0110] Message store providers 330 handle the storage and retrieval ofmessages and other information for the users of client application. Asillustrated in FIG. 4, the message information is organized using ahierarchical system known as a message store, which is implemented inmultiple levels, with containers called folders holding messages ofdifferent types. There is no limit to the number of levels in a messagestore, and folders can contain many sub-folders.

[0111] Transport providers 340 handle message transmission andreception. They control the interaction between the MAPI spooler 310 andthe underlying messaging system 320. They also implement security ifnecessary and take care of any pre-processing and post-processing tasksthat are required. Client applications 300 communicate with thetransport providers 340 through a message store provider 330. When anincoming message is detected, the transport provider informs the MAPIspooler and the message is delivered to the appropriate message store.To handle outgoing messages, the message store moves the message to theoutbound queue, informs the MAPI spooler, and the spooler transfers itto the appropriate transport providers.

[0112] The operation of these MAPI components is illustrated bydescribing the flow of an e-mail message through these components. Theuser of a client application 300 sends a message to one or morerecipients. A message store provider 330 initiates the sending processand formats the message with additional information needed fortransmission. The MAPI spooler 310 receives the message, performs anyrequired preprocessing, and delivers it to the appropriate transportprovider 340. The transport provider 340 gives the message to itsmessaging system 320, which sends it to the intended recipient(s). Whena message is received, the transport provider 340 receives a messagefrom its messaging system 320 and notifies the MAPI spooler 310. Thespooler 310 performs any necessary post processing and informs themessage store provider 330 that a new message has arrived. Thenotification causes the client application 300 to refresh its messagedisplay, which enables the user to read the new message.

[0113] Client application users can access a summary view of themessages contained with each folder or view them individually with aform. Whether the client displays a standard form supplied by MAPI or acustomer form supplied by a form developer depends on the type, orclass, of the message. In FIG. 4, the first folder 400 contains notemessages and uses the MAPI standard note form. The second folder 405contains inventory request messages and uses a custom inventory form.The information on both forms represents the properties, or attributes,of the message. Messages are the units of data transferred from one userto another. Every message contains some text, which is formatted simplyor more intricately depending on the form that is used, and envelopeinformation that is used for transmission.

[0114] A MAPI property is an attribute of a MAPI object, and describessomething about the object, such as the subject line of a message of theaddress type of a distribution list. Every MAPI property has a value, atype, and an identifier. The value is the descriptive data, such as thetext in a message body. The type describes the kind of data, such as astring, numeric, or Boolean. The identifier is the number that uniquelydescribes the property. The identifier and type are combined to form a“property tag,” which is a constant that can be used to easily refer tothe property. Property tags share a common format. they begin with theprefix “PR” and are made up of one or more words that describe theproperty. For example, PR_MESSAGE_BODY is the tag for the message bodyproperty. The property tag and value are stored together in systemmemory 15 (FIG. 1) as a single data structure.

[0115] MAPI also employs “profiles,” which are collections ofinformation about the message services and service providers that a userof a client application 300 wants to be available during a particularMAPI session. Every user has at least one profile. Multiple profiles maybe used in some cases. For example, a user might have one profile towork with a server-based message store service and another profile towork with a message store service on the local computer. A user may haveprofiles on more than one computer. Similarly, a computer may storeprofiles for more than one user. Profiles provide a flexible way toselect combinations of message systems.

[0116] In the MAPI environment, a form is a viewer for a message. Eachmessage has a message class that determines the particular form that isused as its viewer. MAPI defines a few messages classes and hasimplemented the forms for viewing these messages. Client applicationdevelopers can create new message classes and custom forms for viewingmessages with the new classes.

[0117] Every custom form implements a set of standard menu commands(e.g., open, create, delete, and reply) and a set of commands that arespecific to that particular form. These commands are also referred to as“verbs.” FIG. 5 illustrates the MAPI form architecture, which involvesthree main components: a form registry provider 500, a form server 505,and a form viewer 510.

[0118] The form registry provider 500 maintains a library of informationabout all of the forms available on the computer and enables the clientto select a form that is suitable for the message being displayed. Formdata is stored in a form registry 502, which is stored in one of thecomputer's memory storage devices. The form server 505 is responsiblefor displaying the form and providing the information for the display.The form server manages the user's interaction with the form byinterpreting the menu selections and processing the messages. The formviewer 510 is a component within a client application that contains thedisplay and presents it to the user.

[0119] From the foregoing, it will be appreciated that MAPI provides awide variety of features and functions in addition to those included inthe brief description presented above. For additional informationregarding MAPI, the reader may refer to the MAPI documentation, entitledMessaging Application Programming Interface (MAPI) version 1.0, which ispublished by Microsoft Corporation, and which is incorporated herein byreference.

[0120] The Preferred Application Program

[0121] As mentioned above, the preferred embodiment of the presentinvention is represented by the “MICROSOFT OUTLOOK” workgroup personalinformation manager, which is published by Microsoft Corporation. Thepreferred client application is divided into several modules, includinga calendar manager, a task list manager, a contact manager, a messagemanager (e-mail), and a notes manager. In the preferred clientapplication, integration between the modules is both simple andextensive because all information is stored in a MAPI data store, whichis an extensible, object-oriented database. The preferred applicationprogram incorporates the features of MAPI version 1.0.

[0122] All folders (containers) contain objects, or items. In thepreferred application program, there are a variety of kinds of items:e-mail items, appointment items, task items, address items, etc. Itemshave a set of fields and a behavior associated with them. For example,an e-mail item has To, From, CC, Subject, date and time fields amongothers. The behavior of e-mail items includes knowledge of what it meansto Forward or Reply/Reply All.

[0123] Fields are atomic units of data such as the subject and receiveddate of a message. In most cases, a field belongs to an item. A field isdistinct from a “property,” which refers to an underlying atomic unit ofdata at the object storage level, e.g. in a MAPI message. Fields map toproperties, but the mapping is not necessarily one-to-one.

[0124] A user stores information in the form of items. Items, in turn,reside in folders. A message is a collection of properties. Items arecomposed of fields. For example, the “subject” in an e-mail note wouldbe a field called “subject” in the e-mail item. In a MAPI store, objects(messages) have a similar structure, except they are composed ofproperties. In most cases, a field maps directly to a MAPI property.However, there can actually be a many-to-many mapping between fields andthe MAPI properties in which they are stored.

[0125] In the preferred application program, every item is initiallycreated from a template. A template is the “mold” from which new itemsare made and as such describes the fields and the item—the data types,default values, formatting rules, etc. For example, there would be adefault template for each kind of item listed above: appointments, to-doitems, notes, e-mail messages, etc.

[0126] The fields in an item may be different than the fields in thetemplate it came from, because items can have custom fields which otherinstances of the templates do not have. An item always has a templateassociated with it, however, even if it has so many custom fields thatit bears little resemblance to the original templates.

[0127] The user creates a template by creating an item, customizing itby adding or deleting fields as necessary, setting initial values forfields and then saving it, giving the template a name. The user caneither create a new template (by giving it a new name) or replace theexisting one. One way this would be used is to make a template out of anitem which has one or more custom fields; if the user thinks that anitem with that set of fields is useful for more than one or two items,this allows an easy way to do so.

[0128] From this brief description, those skilled in the art willappreciate that the preferred application program provides a widevariety of features and functions in addition to those included in thebrief description presented above. For additional information regardingthe “MICROSOFT OUTLOOK” application program, the reader may refer to thedocumentation that is distributed with the program.

[0129] The Preferred Method for Automatic Name Checking

[0130] When an e-mail user composes an e-mail message, the useridentifies the recipient(s) of the message by entering one or moredisplay names in the message's address field. Before the message canactually be transmitted by the e-mail system, the system must match eachdisplay name entered in the address field to the specific e-mail address(or address book entry) of a registered user. The e-mail addresses ofall registered users are referred to as aliases, and are maintained in asystem directory. The directory may cross reference each alias to otherinformation about the user, such as first and last name, department,office location, and phone number. The process of matching the displayname(s) to an e-mail address or alias is referred to as “resolving” thenames.

[0131] In most e-mail systems, the display names are resolved when theuser attempts to send the message, or when the user invokes a “checknames” command. In either case, the e-mail program resolves unambiguousdisplay names without requiring any additional input from the user. Inorder to resolve ambiguous display names, the e-mail program displays adialog box that allows the user to select the intended recipient from alist of possible matches.

[0132] The present invention provides a method for resolving names inthe background, which means that the user may continue to use thecomputer to perform other tasks while the display names are beingresolved. In the preferred program, the display names are typicallyresolved while the user is composing the remainder of the e-mailmessage. The present invention also provides an improved system forresolving ambiguous names. The present invention automatically remembershow ambiguous names are resolved the first time they are encountered anduses that information to resolve those names in the future.

[0133]FIGS. 6 and 7 illustrate the user interface that is employed bythe preferred embodiment of the present invention. FIGS. 6a-6 cillustrate a process for resolving names in accordance with thepreferred embodiment of the present invention. FIGS. 7a-7 c illustratethe operation of the preferred automatic nickname resolution feature.

[0134]FIG. 6a illustrates an address field 600 of an e-mail form that isbeing used to compose a message item. The form and address field 600 aredisplayed on the monitor 31 (FIG. 1). At this point, the user has typedin three display names, which provide identifying information about eachof the intended recipients. The entered display name may include all orpart of the intended recipient's first name, last name, and/or e-mailalias. Each display name is preferably separated by an appropriatedelimiter, such as a semicolon.

[0135] As soon as the user moves the cursor to another field on thee-mail form, the e-mail program module begins to resolve the recipientnames in the background, while the user continues to compose theremainder of the message. As mentioned above, “resolving” the namesmeans attempting to match the display names in the address field tospecific user aliases that are included in a centralized address book ordirectory, which is typically stored on a remote server, such as remotememory storage device 33 (FIG. 1). In the preferred application program,the e-mail system searches several address book fields in an effort tomatch the display names with the first name, last name, and/or alias ofa registered user. Thus, in this example, the e-mail program willattempt to match “billb,” “sm henry,” and “patterson” with specificaddress book entries belonging to registered users.

[0136]FIG. 6b illustrates the results of the effort to resolve thenames. If a display name is unambiguous and matches only one registereduser, the name of that user is inserted in the address field. If thedisplay name is ambiguous, the e-mail program indicates that the displayname needs to be manually resolved by displaying the display name and apredetermined indicia, such as a squiggly line 605 beneath the displayname. FIG. 6b indicates that the display names “sm henry” and“patterson” were unambiguously matched to “Henry Smith” and “RogerPatterson,” respectively. Names that are unambiguously matched appearwith a regular underline beneath the display name. The squiggly linebeneath the display name “billb” indicates that the e-mail system wasunable to find a unique match for that display name.

[0137]FIG. 6c illustrates the process by which a user manually resolvesambiguous names. In the preferred system, the user places the cursorover the unresolved display name and clicks the right mouse button. Inresponse, the e-mail program displays a context menu 610 that includes alist of possible matches. In this case, the possible matches includeusers whose first name is Bill and whose last name begins with theletter “B.” If the intended recipient's name is displayed in the contextmenu 610, the user may select the correct name from the list.

[0138] If the intended recipient's name is not displayed in the contextmenu 610, the user may choose one of several options. For example, the“show more names” command in the context menu 610 indicates that thereare more possible matches. If the user selects this command, a dialogwill display additional names from which the user may select. The“create new address for billb” option in the context menu 610 allows theuser to create an entry in his or her personal address book. Thoseskilled in the art will appreciate that this is typically used to storeaddresses of e-mail recipients who are not registered users on the locale-mail system. For example, if “billb” is a friend that the usercommunicates with via Internet e-mail, the user can record Bill'sInternet e-mail address in his or her personal address book. The“address book” command in the context menu 610 instructs the e-mailprogram to display the e-mail system's complete address book, from whichthe user may select the e-mail address of the intended recipient.

[0139] In addition to the features described in conjunction with FIGS.6a-c, the preferred e-mail program module automatically creates a listof nicknames that are based on how the user resolves ambiguous displaynames. This allows a user to use convenient, but ambiguous, displaynames to identify intended recipients. For example, if the userfrequently sends e-mail messages to Bill Bailey, he or she may prefer touse “billb” as a convenient nickname although it is ambiguous. In FIG.7a, the user has entered “billb” in the address field 700. As before,the e-mail system will attempt to match “billb” to an e-mail alias.However, an e-mail system in accordance with the preferred embodimentwill check a nicknames memory cache, which is stored in system memory 15(FIG. 1), to see if the user has manually resolved the ambiguous displayname “billb” in the past. If so, the e-mail program will display theprevious recipient's full name and indicia that indicates this is anickname. In the preferred e-mail program, resolved nicknames aredisplayed with blue dashed lines beneath them. In this example, thedashed line 705 beneath “Bill Bailey” indicates to the user that BillBailey is the user that is currently associated with the nickname“billb” (FIG. 7b).

[0140] If Bill Bailey is the intended recipient, the user need not takeany other action before sending the message. However, if the userintended to send the message to someone other than Bill Bailey, the usermay override the nickname using a context menu 710 (FIG. 7c). Thisprocess is identical to the process for resolving names described inconjunction with FIG. 6b, except that the first name listed in thecontext menu 710 is the name to which the nickname has been matched. Ifthe user overrides the previous nickname, the “billb” name in thenicknames memory cache is redefined to correspond to the most recentintended recipient. Thus, a nickname appears only once in the nicknamelist and is overwritten as changes or corrections are made by the user.

[0141]FIG. 8 is a flow diagram illustrating the preferred process 800 bywhich a user enters and resolves display names. Those skilled in the artwill appreciate that although the method 800 is described primarily interms of steps carried out by a user, the present invention is acomputer-implemented process that is carried out by a computer inresponse to input from the user and instructions provided by thepreferred e-mail program module.

[0142] The process 800 begins at start step 805 and proceeds to step 810when the user selects the command that creates a new message. At step815 the user enters display names that indicate the identity of the ofthe intended recipients. As mentioned earlier, the display names mayinclude all or part of the recipient's first name, last name, or e-mailalias. At step 820 the user moves the cursor out of the address field600 (FIG. 6) and continues to compose the remainder of the message.

[0143] At step 825 the user reviews the addresses that are displayed inthe address field 600 (FIG. 6). At this point, the e-mail system willhave attempted to resolve the names in the background and displayed theresults in the address field. At step 830 the user determines whetherany of the display names need to be resolved manually. As mentionedabove, this will be the case for ambiguous display names, which arepreferably displayed with a squiggly line beneath them, or forincorrectly resolved nicknames. If none of the display names need to beresolved manually, the user goes to step 835 and sends the e-mailmessage. From there, the method terminates at step 840.

[0144] If, at step 830, the user determines that one or more of thedisplay names needs to be manually resolved, the user goes to step 845.At step 845 the user manually resolves the display names using thecontext menu and other options described above in conjunction with FIGS.6c and 7 c.

[0145]FIG. 9 is a flow diagram that illustrates the preferred method 900by which the computer attempts to resolve the display names entered inthe address field. Although the method 900 is described in terms oftasks carried out by a computer, those skilled in the art willappreciate that the present invention is a computer-implemented processthat is carried out by the computer in response to input from the userand instructions provided by the preferred e-mail program module.

[0146] The method 900 begins at start step 905 and proceeds to step 905when the user moves the cursor out of the address field and to anotherfield on the e-mail form. At step 910 the computer first checks to seeif the display names in the address field corresponds to a nickname thatis stored in the nicknames memory cache, which is stored in thecomputer's memory storage devices as part of the user's profile. At step915 the computer determines whether any display names remain to beresolved. If all of the display names were resolved by matchingnicknames, the computer goes to step 920 and displays the address datawith the proper indicia. As discussed above, in the case of nicknames,the full name of the recipient is inserted in the address field and ispreferably marked with a blue dashed line beneath it. From step 920, thecomputer proceeds to step 925 and the method 900 terminates.

[0147] If, at step 915 the computer determines that there are additionaldisplay names to resolve, the computer goes to step 930 and attempts toresolve the remaining display names. In the preferred e-mail program,this is accomplished by calling the appropriate MAPI functions, such asMAPIResolveName. Those skilled in the art will appreciate that this MAPIfunction handles the addressing chore of resolving informal names withactual e-mail aliases. From step 930 the computer proceeds to step 920and displays the address data with the proper indicia. As discussedabove, the full name of unambiguous recipients is inserted in theaddress field. Ambiguous addresses are preferably marked with a squigglyline beneath them. From step 920, the computer proceeds to step 925 andthe method 900 terminates.

[0148]FIG. 10 is a simple state diagram that illustrates the method 1000by which the computer creates and maintains the list of nicknames. Thisprocess has also been described in conjunction with FIGS. 6 and 7. Themethod 1000 begins at the idle state 1005. At this point, the computerhas displayed at least one ambiguous display name or nickname in theaddress field. When the user selects a nickname or an ambiguous displayname, the computer goes to state 1010 and displays a context menu 610(FIG. 6) that includes a list of possible matches (see FIGS. 6c and 7c).

[0149] When the user selects one of the names from the context menu, thecomputer goes to state 1015 and updates the nickname list. As describedabove, the nickname list is stored in a memory cache that is part of theuser's profile, and is used to automatically create nicknames. Thenickname is stored with the actual e-mail alias or address book entry ofthe intended recipient. If this is the first time a nickname isresolved, it is added to the nickname cache. If the nickname was earliermatched to a different alias, the nickname list is updated to reflectthe current recipient. In the preferred system, the nickname file ispart of the user's profile, which is stored on one or more of thecomputer's memory storage devices.

[0150] When a user enters an Internet e-mail address in the form ofxxxxx@yyyyy.zzz, the user need not create a new name in his or herdirectory before the name can be resolved. The preferred e-mail systemsimply identifies such an address as an Internet address and resolves itwithout further user intervention.

[0151] Those skilled in the art will appreciate that in the preferredapplication program, addresses are also resolved when the user sends themessage or if the user selects the “check names” command. As such, thepreferred embodiment is implemented without requiring any changes tothese features. In addition, if the user sends the message or selectsthe “check names” command while the e-mail program module is operatingin the background, the processes or threads associated with the e-mailprogram are automatically halted. In addition, if the user attempts tosend the message without resolving the ambiguous display names displayedby the e-mail program, the process defaults back to the normal processfor resolving names, which displays a dialog box from which the usermust choose the correct name.

[0152] From the foregoing description of the various features, thoseskilled in the art will appreciate that the name checking feature of thepreferred e-mail program automatically resolves display names while auser composes a message and simplifies the process of manually resolvingambiguous names by providing multiple options for resolving theambiguities. In addition, the preferred e-mail program automaticallycreates and maintains a list of nicknames.

[0153] The Preferred Method for Providing Message Flags

[0154] E-mail messages typically fall into one of three categories: (1)those in which the recipient is asked or instructed to do something; (2)those which prompt the recipient to take some form of action though heor she is not explicitly requested by the sender to do so; and (3)information that requires no follow-up action. Generally, an e-mailrecipient will read a message, decide what response is required andeither act on that decision immediately or close the message andpostpone the required action until later. Although a recipient may knowthat some form of follow-up action is required, once the message isclosed it is often easily overlooked or lost in the clutter of the othermessages in the inbox. This is especially likely if the recipientreceives a large number of e-mail messages.

[0155] The prior art has not provided any convenient or effective wayfor senders or recipients to flag messages that require follow-upaction. An aspect of the present invention allows a user (sender orrecipient) to attach a flag, or message flag, to an e-mail message. Themessage flag clearly identifies the follow-up action (e.g., fax report),or action item, that is required to deal with the message, and may alsoinclude a deadline. The message flag and deadline draw the recipient'sattention to the main action item associated with the message.

[0156] Message flags make it easier for the recipient of e-mail messagesto organize and manage his or her inbox. With message flagging, ane-mail recipient may work through his or her inbox and flag messagesthat require some form of follow-up action. Once the follow-up action iscomplete, the recipient may mark the message to so indicate thecompleted state. If an item is flagged with a deadline and has not beenmarked as complete, the e-mail program will provide an alarm at apredetermined period of time prior to the deadline. Similarly, if anitem is marked with a deadline that arrives before the item is marked ascomplete, the e-mail program will change the display attributes of theoverdue item, thus making it readily apparent to the recipient. Themessages may also be sorted or grouped according to whether they includemessage flags, by deadline, or by whether they are marked as completed.These features allow the user to effectively manage the tasks thatresult from incoming e-mail messages.

[0157] Turning now to FIGS. 11-18, the preferred method for providingmessage flags will now be described. As discussed above, the messageflagging features form a part of the preferred application program,which is the “MICROSOFT OUTLOOK” personal information manager, publishedby Microsoft Corporation. The preferred application program includes avariety of program modules that are tailored to various tasks, includingscheduling, electronic mail, task management (“to-do” lists), andcontact management. This aspect of the present invention deals primarilywith the features of the e-mail program module.

[0158]FIG. 11 illustrates the preferred data structure in which data isstored in an e-mail message. Generally, an e-mail message (also referredto as an e-mail item) includes a plurality of properties. Each propertyis associated with data that represents the value of that property. Inmost cases, the properties correspond to a field that is displayed bythe e-mail program module. For example, most e-mail items include thefollowing properties, which correspond to fields displayed on the e-mailform, as shown in Table I. TABLE I Property Tag Value (data) Sender Thename of the user that originated the e-mail item Recipient(s) The nameof the recipient(s) of the e-mail item Subject The subject of the e-mailmessage Body The text of the e-mail message

[0159] A user composes an e-mail message by entering values in displayedfields that correspond to the properties. Those skilled in the art willappreciate that most e-mail modules automatically insert the name of thesender in the sender field. When an e-mail message is transmitted to arecipient, its constituent properties and their associated values aretransmitted to the recipient via a network.

[0160] As illustrated in FIG. 11, the preferred e-mail module uses threeadditional properties to provide the message flag features. Theadditional properties include status 1100, message flag 1105, and duedate 1110 properties. Each property consists of the property tag and theassociated value. The status property 1100 indicates one of threestates: (1) there is no flag associated with the message; (2) the e-mailitem includes a message flag and is not complete; and (3) the e-mailitem includes a message flag and is complete. The message flag property1105 indicates the action item associated with the message. The due dateproperty 1110 indicates a deadline for completing the action item.

[0161] As mentioned above, the preferred application programincorporates the features of MAPI version 1.0. Like other applicationprogramming interfaces (APIs), MAPI provides a variety of standardizedservices that simplify the process of writing code to carry out certainfunctions. In particular, the MAPI features facilitate the addition ofnew properties. This is accomplished by calling the appropriate MAPIfunction, SetProps, and providing the name and value of the newproperty. The properties are saved as part of the message item.Additional information is available in the MAPI specification.

[0162]FIG. 12 is a flow diagram illustrating the preferred stepsperformed by a user in order to create an e-mail message that includes amessage flag. Those skilled in the art will appreciate that although themethod 1200 is described primarily in terms of steps carried out by auser, the present invention is a computer-implemented process that iscarried out by the computer in response to input from the user andinstructions provided by the preferred e-mail program module.

[0163] The method 1200 begins at start step 1202 and proceeds to step1205 when the user decides to create a new e-mail message. At step 1205,the user performs the steps associated with the creation of aconventional e-mail message, including identifying the recipient(s) ofthe message, entering a subject, and typing the body of the message.

[0164] At step 1210 the user decides whether to add a specific actionitem (message flag) to the message. If not, the “no” branch is followedand the user proceeds to step 1215. At step 1215 the user sends thee-mail message, which includes the conventional types of data. Once themessage is sent, the method 1200 ends at step 1220.

[0165] If, at step 1210, the user decides to add a specific action itemto the message, the “yes” branch is followed to step 1225 where the userenters the message flag. This is accomplished by first selecting a “flagmessage” command. In the preferred application program, this causes thecomputer to display a dialog box that provides a field for the user toenter the action item (i.e., the flag) and a due date, if one isdesired. When entering the message flag, the user may type the flag, orselect from a list of common actions items that are displayed in thedialog box. These items include entries such as call, follow-up,forward, read, reply, etc. The list also includes entries such as “foryour information” and “no response necessary” if the user wants to makeit clear to the recipient that no response is expected.

[0166] After the user has entered the flag at step 1225 the userproceeds to step 1230 and determines whether to add a due date to themessage. If not, the “no” branch is followed to step 1215 where the usersends the message. If the user wants to add a due date, the “yes” branchis follows to step 1235 where the user enters the deadline, whichincludes a date, and may also include a time. After the user enters thedue date at step 1235 the user goes to step 1215 and sends the message.

[0167]FIG. 13 is a state diagram illustrating the preferred processperformed by a computer that is being used to create an e-mail messagethat includes message flags. Although the method 1300 is described interms of tasks carried out by a computer, those skilled in the art willappreciate that the present invention is a computer-implemented processthat is carried out by the computer in response to input from the userand instructions provided by the preferred e-mail program module.

[0168] The method 1300 begins at state 1305 with the computer in an idlestate as it relates to instructions provided by the e-mail programmodule. When the user selects the command for creating a new message,the computer proceeds to state 1310, where it receives the informationthat is typically associated with a conventional e-mail message. Asmentioned above, this includes receiving data indicative of therecipient(s), subject, priority, and body, and storing this data inassociation with the corresponding properties that constitute the e-mailmessage item. If the user then selects the “send” command, the computergoes to state 1315 and transmits the e-mail message item. Those skilledin the art will understand that this may be accomplished by calling theMAPISendMail and SubmitMessage functions, which carry out the specificsteps necessary to send an e-mail message item, including all of theconstituent properties and associated data. After the message is sent,the computer returns to the idle state 1305.

[0169] Referring again to state 1310, if the user selects the “flagmessage” command, the computer proceeds to state 1320. At state 1320 thecomputer receives the message flag data and due date data (if provided)from the user and stores it in association with the corresponding e-mailmessage properties. As described earlier, the preferred e-mail programprovides message flags by adding three properties to the e-mail messageitem. These include the status, message flag, and due date properties,which were discussed in conjunction with FIG. 11. When the message flagis added at state 1320, the action item entered by the user is storedwith the message flag property and the deadline, if any, is stored withthe due date property. In the preferred e-mail system, the default valuefor the flag is “follow-up” and for the due date is “none.” When themessage flag is entered, the computer alters the status property toindicate that the message item includes a message flag and that the itemis not yet completed. The data associated with the status propertytypically is not displayed to the sender. When the user then selects the“send” command, the computer goes to state 1315 and transmits the e-mailmessage item in the manner described above. From there, the computerreturns to the idle state 1305.

[0170]FIGS. 14 and 15 illustrate the information that is displayed to arecipient of e-mail messages that include message flags. FIG. 14illustrates a “list view” of e-mail messages received by a user of thepreferred e-mail program. The list view is suitable for displaying alist of the messages in a user's inbox. FIG. 15 illustrates the messageview, which displays the complete content of a message that has beenopened by the user of the preferred e-mail program.

[0171]FIG. 14 illustrates a default list view 1400, which adds a“status” column 1405 to the information typically displayed by prior arte-mail programs. The “status” column 1405 indicates whether each e-mailmessage item includes a message flag and whether the action item hasbeen marked by the recipient as being complete. In FIG. 14, the messageitems that include a message flag are marked with either a “-” or a “✓.”The “✓” indicates that the recipient has marked the item as beingcomplete. The “-” indicates that the item has not been completed. Inanother embodiment, the “-” and “✓” icons are replaced with red andwhite flags. Messages without a message flag do not include any mark inthe “status” column. In the preferred application program, the list viewmay be altered to display other combinations of information, such as thecontent of the message flag.

[0172]FIG. 15 illustrates the information that is displayed in themessage view for the preferred e-mail program. This view is used todisplay the complete content of an e-mail message item. The message viewis displayed after a user opens an e-mail message from the list view(FIG. 14). In the message view, the preferred application programdisplays the data that is associated with prior art messages, includingthe sender, the recipient(s), the subject, and the body of the message.The date and time that the message was completed may also be displayed.In addition, messages that include message flags are displayed with analert line 1500, which includes the text of the message flag 1505 andthe due date 1510 (if any). In addition, the alert line 1500 includes acheck box 1515 that indicates whether the action item is complete. Whenthe message is first opened, this box is not checked. The user may clickon the box to indicate that the associated action item has beencompleted.

[0173]FIG. 16 is a flow diagram that illustrates the steps that may beperformed by the recipient of e-mail messages. As mentioned above, thepresent invention is a computer implemented process that is carried outby the computer in response to input from the user and instructionsprovided by the e-mail program.

[0174] As discussed earlier, in the context of message flagging, therecipient has several options regarding a response to e-mail messageitems. Those skilled in the art will appreciate that the optionsdiscussed in conjunction with FIG. 16 are provided in addition toconventional options, such as deleting, replying to, and forwarding amessage. Generally described, the recipient of e-mail messages may readmessages, add or alter message flags, and sort and group messages basedon specified properties.

[0175] The method 1600 begins at start step 1602 and proceeds to step1605 when the user opens the e-mail program module and reviews the itemsin his or her inbox, which are displayed in the list view (FIG. 14). Atthat point, the user may decide to read a message or to take some otheraction. If the user decides to read one of the messages, the user goesto step 1610 and opens the selected message. In the preferred program, amessage may be opened by double clicking on the selected message or byselecting the message and invoking the read command.

[0176] Once the user has read the message the user goes to step 1615 anddetermines whether the message includes a message flag. If not, the usergoes to step 1620 and decides whether to add a message flag, which wouldbe appropriate if the user decides some follow-up action is required. Ifthe user is satisfied that the message does not need a message flag, theuser closes the message (step 1625). The method 1600 terminates at step1630.

[0177] If, at step 1615, the user sees that the message includes amessage flag, the user goes to step 1635 and determines whether theaction item and due date (if any) associated with the message flag aresatisfactory. If so, the user goes to step 1625 and closes the message.If the message flag and due date are not satisfactory, the user goes tostep 1640 and edits the information. For example, if the message flagand deadline indicate that a task must be completed by Friday, but theuser will be out of the office on Friday, the user may edit the due datedata to indicate that the task must be complete by Thursday at 5:00 p.m.Similarly, the user can edit the message to indicate that a task hasbeen completed. After the message flag is edited, the user goes to step1625 and closes the message.

[0178] Returning now to step 1620, if the user decides to add a messageflag to a message that does not include one, the user goes to step 1645.At that point, the user selects the appropriate command and adds themessage flag and, if desired, due date information. This information isstored in association with the corresponding message item properties andbecomes part of the message item. Once the message flag is added, theuser goes to step 1625 and closes the message.

[0179] Returning now to step 1605, the user may also decide to performssteps to organize or manage his or her inbox. For example, the user maychoose to sort messages by going to step 1650. As in prior art e-mailprograms, the program rearranges the e-mail messages in the list viewaccording to the values in one or more of the selected properties. Forexample, the user may sort the message by date received, by whether theyare complete, etc. The method 1600 then terminates at step 1630.

[0180] From step 1605 the user may also decide to group the messagesaccording to the values associated with certain properties. Groupingdiffers from sorting because grouped messages are displayed in groupswith dividers or separators between them. At step 1655, messages may begrouped according to whether they require follow-up, the type offollow-up required, and the due date. The method 1600 then terminates atstep 1630.

[0181]FIG. 17 is a state diagram illustrating the preferred tasksperformed by the computer in response to decisions made by the user, asdescribed with respect to the flow diagram of FIG. 16. Those skilled inthe art will understand that the computer is operative to carry out themethod 1700 in response to various inputs provided by the user. Themethod 1700 begins at state 1705 with the program in the idle state.

[0182] If the user invokes an “open message” command, the computer goesto state 1710 and opens the selected message. This allows the user toread the entire content of the message item. From there, the computerwill do one of several things based on input from the user. If the userinvokes the “close message” command, the computer goes to state 1715,closes the message. From there, the computer returns to the idle state1705.

[0183] If, at state 1710, the user invokes the add message flag command,the computer goes to state 1720, where it receives message flag and duedate data from the user and stores the data in association with thecorresponding properties that constitute the message item. From there,the computer returns to the idle state 1705.

[0184] If, at state 1710, the user invokes the edit message flagcommand, the computer goes to state 1725, where it receives revisedmessage flag and due date data from the user and stores the revised datain association with the corresponding properties that constitute themessage item. From there, the computer returns to the idle state 1705.

[0185] As discussed in conjunction with FIG. 16, the user may decide tosort or group the messages in the inbox. Referring again to the idlestate 1705, the computer proceeds to state 1730 if the user invokes thesort command and to state 1735 if the user invokes the group command. Asmentioned above, the computer sorts messages by rearranging the order inwhich they are displayed in the list view. The order is determinedaccording to the values of one or more of the properties selected by theuser. For example, the user may sort the message by date received, bywhether they are complete, etc. Those skilled in the art will appreciatethat the sort function may be performed by calling the appropriate MAPIfunction, SortTable. Similarly, when messages are grouped, they aredisplayed in groups with dividers or separators between them. Messagesmay be grouped according to whether they require follow-up, the type offollow-up required, and the due date. Those skilled in the art willappreciate that the group function may be performed by calling theappropriate MAPI function, SortTable. After the computer groups or sortsmessages, the computer returns to the idle state 1705.

[0186]FIG. 18 is a flow diagram illustrating the preferred process forusing message flags and deadline data for generating reminders for theuser. These steps are carried out by the computer in response toinstructions provided by the e-mail program. In one aspect, the methoddisplays a reminder at a predetermined period of time prior to the duedate. In another aspect, the method changes the display attributes of amessage item in order to indicate that the due date is past. Thoseskilled in the art will appreciate that these functions are performed bycomparing the due date data for each message to the current time. In thepreferred e-mail program, this comparison is performed at various,predetermined times. For example, the comparison is made when a messageis opened, at a predetermined time (e.g. midnight), and when a list viewis redrawn, such as when a new message is received or the user opens afolder that contains messages.

[0187] At the times described above, the computer 1800 examines eachmessage and determines whether the due date data indicates that areminder is needed or that the action item is past due. The processbegins at start step 1802 and proceeds to step 1805, where the computerdetermines whether the first message requires a reminder. This isaccomplished by comparing the due date data from the first message withthe current time. If the due date data is within a predetermined timeperiod (e.g., 2 days) of the current time, the computer goes to step1810 and generates a reminder message, which is displayed to the user.After the reminder is displayed, or if no reminder is required, thecomputer proceeds to step 1815.

[0188] At step 1815 the method determines whether the due date is pastdue. This is accomplished by comparing the due date data to the currenttime. If the item is past due, the method goes to step 1820 and changesthe display attributes of the past due message item. For example, in thelist view (FIG. 14), past due items may be displayed in red. After thedisplay attributes are altered, or if the item is not past due, themethod proceeds to step 1825.

[0189] At step 1825, the method determines whether the inbox or folderincludes other messages that need to be checked. If so, the methodreturns to step 1805 and checks the due date of the next message. Ifnot, the method terminates at step 1830.

[0190] From the foregoing description of the various features, thoseskilled in the art will appreciate that message flagging facilitatescommunication between the sender and recipient of e-mail messages andfacilitates the recipient's organization and management of e-mailmessages. This is accomplished by allowing a sender to clearly indicatea follow-up action and a due date. The recipient is able to clearlyidentify those messages that require some type of follow-up action andthe deadline for that follow-up. Furthermore, the invention providesreminders of upcoming due dates and an indication that an item is pastdue.

[0191] In summary, the present invention benefits an e-mail sender byallowing him or her to provide a separate message flag and due dateregarding follow-up actions associated with a message. The presentinvention benefits recipients by allowing a recipient to determine thestatus of a message and to edit the message flags. Furthermore, thepresent invention helps the recipient organize his or her inbox byproviding sorting and grouping functions. Project management is alsofacilitated by the provision of reminders and past due notification.

[0192] The Preferred Method for Utilizing Custom Forms

[0193] As described above, in the MAPI environment, a form provides atemplate that is used to display the contents of an e-mail message. Forexample, an e-mail message typically includes an address field, a “From”field, a “Subject” field, and a “Body” field. The user composes ane-mail message by entering data into the appropriate fields and thensends the message to the recipient. For example, a user may enter“Lunch” in the “Subject” field and enter “Where would you like to eat?”in the “Body” field. The form allows the sender and recipient of ane-mail message to view the fields and data entered into those fields. Aform contains layout information that specifies the layout, orarrangement, of the fields.

[0194] As previously discussed, there are times when a user feels thatavailable forms simply do not meet his or her requirements and that itwould be useful to create a custom form that allows the viewing ofadditional fields. A custom form is one in which the user has addedfields, deleted fields, and/or rearranged fields to suit a particularneed. As those skilled in the art will understand, several priorapplication programs allow users to create custom forms. These programsinclude the forms design utility in the “MICROSOFT EXCHANGE” programpublished by Microsoft Corporation, the “LOTUS NOTES” groupware messageapplication program published Lotus Development Corporation, and the“JETFORM FOR E-MAIL” program published by JetForm Corporation.

[0195] In the prior art, after the creation of a custom form, the customform is typically “published,” or stored on a central file server. Eachuser was then required to install the form on their computer. Beforeusing the custom form, all users, both users sending a message itemcontaining the custom form and users receiving a message item containingthe custom form, had to install the custom form on their operatingsystem. Thus, the prior art has not provided a convenient method forusers to quickly create a custom form and to send and receive a customform.

[0196] As mentioned earlier, an e-mail message, or e-mail item, includesa plurality of properties. Each property includes a property tag andvalue, which are stored together in system memory 15 (FIG. 1) as asingle data structure. In most cases, the properties correspond to afield that is displayed. FIG. 19 illustrates an e-mail message item 1900that includes a plurality of properties. These include the standardproperties 1905, such as a “sender” property 1910, a “recipient(s)”property 1915, a “subject” property 1920 and a “body” property 1925.

[0197] The preferred e-mail module uses an additional property toprovide a method and system for creating a message item that uses acustom form. Generally described, a description of the custom form isstored in a property of the e-mail message, and is transmitted to therecipient as part of the message. This eliminates the need for the formto be installed on the recipient's computer prior to receiving the newmessage.

[0198] In the preferred e-mail system, an existing form, or standardform, can be modified by the user by rearranging fields and adding newfields, if necessary, to create the layout of fields desired by theuser. The modified form is referred to as a custom form. As illustratedin FIG. 19, in the preferred embodiment, a value corresponding to thelayout information of the custom form and a “form” property tag arestored together as a “form” property 1930 in the e-mail item 1900. The“form” property is sent to the recipient with other properties of themail item. The value stored in the form property 1930 contains layoutinformation for the standard properties 1905 and the custom properties1935. The standard properties correspond to the fields that wereincluded in the standard form. The custom properties correspond to thefields that were added by the user when customizing the standard form.In contrast to the prior art, the preferred embodiment does not requirethat the form be previously “published” or that the user or therecipient install the form in a memory device before sending orreceiving a message item that uses the form.

[0199] When a recipient receives an e-mail message, it is determinedwhether the message item has a “form” property. If the message itemincludes a “form” property, then the value in the “form” property isread to extract layout information. The layout information is used todisplay the message item, including the fields, in the proper placementand arrangement.

[0200] Preferably, the creation of a custom form is accomplished usingthe preferred application program, which is the “MICROSOFT OUTLOOK”personal information manager. Thus, the following description of thecreation of a custom form is given with reference to the commands andsteps executed when creating a form using the “MICROSOFT OUTLOOK”personal information manager.

[0201]FIG. 20 is a flowchart, from the sender's perspective, of thesteps performed in creating and sending an e-mail message that uses acustom form. Although the method is described below in the context of auser executing certain steps and a computer performing certain steps,those skilled in the art will understand that the present invention is acomputer-implemented process carried out by a computer in response toboth user input and instructions from an e-mail program module.

[0202] The method 2000 begins at the start step 2002 and proceeds tostep 2005 when the user opens a new e-mail message. As those skilled inthe art will understand, the new message will be displayed using apreviously installed form, or standard form. A standard form supplied byMAPI includes fields such as an address field, a “From” field, a“Subject” field, and a “Body” field that are commonly used in a message.

[0203] At step 2010, the user decides whether to use one of thepreviously installed forms or to create a custom form for the e-mailmessage. If the user decides to use a previously installed form, theuser proceeds to step 2015 and composes the e-mail message. In otherwords, at step 2015, the user performs the steps associated with thecreation of a conventional e-mail message, including identifying therecipient(s) of the message, entering a subject, and typing in the textof the message. After the user has composed the message, then the usersends the message. Once the message is sent, the method 2000 ends atstep 2020.

[0204] If, at step 2010, the user decides to design a custom form forthe message, the user proceeds to step 2025 and customizes the form, ordesigns the custom form. This is accomplished by first selecting a“design forms” option. In the preferred application program, selectingthe “design forms” option shifts the application program into designmode. When the preferred application is in design mode, a dialog boxknown as a field chooser is displayed. The field chooser 2100, which isshown in FIG. 21, is a dialog box that provides a list of fields thatthe user may add to the displayed form. For example, a field chooser maycontain a list of fields such as “Cc” 2105, “Conversation Topic” 2110,“Do not Auto Archive” 2115, “From” 2120, “Icon” 2125, “Importance” 2130,“Message” 2135, “Received” 2140, and “Sent” 2145.

[0205] When customizing a form, the user selects a field from the fieldchooser 2100 and adds this field to the form. The field chooser alsoprovides an option that allows a user to create a new field, if thefields listed in the field chooser do not meet the needs of the user.The user preferably creates a new field by selecting the “new field”option 2150 in the field chooser. Then, the user enters a name, type,and format for the new field. After the new field is created, thepreferred application program adds the new field to the field chooser.Then, the user can select the new field from the field chooser and addit to the standard form. It will be understood by those skilled in theart that any previously installed form can be customized using themethod outlined above.

[0206] Referring again to FIG. 20, after the user has designed the format step 2025, the user proceeds to step 2030 and returns the applicationprogram to run mode. This is accomplished by selecting a “run mode”command.

[0207] After returning the application program to run mode, the usercomposes and sends the message at step 2015 as described above. Themethod then ends at step 2020.

[0208]FIG. 22 is a state diagram illustrating the functions performed bya computer that is being used to create an e-mail message that uses acustom form. The method 2200 begins at state 2205 with the computer inan idle state as it relates to instructions provided by the e-mailprogram module. When the user selects the command for creating a newmessage, the computer proceeds to step 2210, where it displays thestandard form for an e-mail message. The standard form includes fieldsto enter data or compose the message. If the user enters data for one ormore of these fields, the computer goes to state 2215 and stores theconstituent data in properties of the e-mail item corresponding to thesefields. When the user selects the “send” command, then the computer goesto state 2220 and transmits the e-mail message item. After the messageis transmitted, the computer returns to the idle state 2205.

[0209] Referring again to state 2210, if the user chooses the “designforms” command, the computer proceeds to state 2225. At state 2225, thecomputer shifts the preferred e-mail program module from run mode todesign mode. In design mode, the user may customize, or edit, thedisplayed form by adding and/or rearranging fields. When the userselects the “design forms” option, the computer also displays a fieldchooser dialog box at state 2225.

[0210] If the user selects a field from the field chooser dialog box tobe added to the standard form, then the user drags the field off of thefield chooser dialog box and onto the custom form. The user “drags” thefield off of the field chooser dialog box using a mouse 29 (FIG. 1) orsimilar input device. The computer adds the field to the displayed formand continues to display the field chooser dialog box at state 2225.

[0211] If the user selects the “new field” command, the computerproceeds to state 2230. At state 2230, the computer displays a new fielddialog interface. The new field dialog interface includes blanks toenter the name, type, and format of the new field. A toolbox is alsodisplayed. The toolbox has buttons corresponding to different tools thatcan also be used to create new fields on the form. For instance, theuser can select the radio button tool from the toolbox and create a newradio button on the form. After the user enters the name, type, andformat of the new field or adds a field using the toolbox then the userselects the “OK” command. After the user selects the “OK” command, thecomputer returns to state 2225. As described above, at state 2225, thecomputer displays a field chooser dialog box. After the user has added anew field, the computer will display the field chooser dialog boxincluding the new field that was added.

[0212] Referring again to state 2225, if the user is finished addingfields, then the user closes the field chooser dialog box. When thefield chooser is closed, the computer proceeds to state 2235. At state2235, the computer displays the standard form and the new fields thathave been added to the standard form. The user can rearrange the fieldsuntil the fields are in the location and position desired by the user.When the user has finished rearranging the fields, the user selects acommand to return to run mode and the computer proceeds to state 2240.At state 2240, the computer displays the custom form, that is, thestandard form with added fields, with the fields in the positiondetermined by the user. In run mode, the user may enter datacorresponding to the fields of the custom form, but may not rearrangefields or add and delete fields as can be accomplished in design mode.

[0213] If the user composes the message, i.e. enters data correspondingto one or more fields of the custom form, the computer proceeds to state2215 and the data entered into the fields is stored in the propertiescorresponding to the fields. When the user selects the send command, thecomputer proceeds to state 2220 and transmits the e-mail item. After themessage is sent, the computer returns to the idle state 2205.

[0214]FIG. 23 is a representative example of the user interface that isdisplayed by the preferred e-mail program module to the sender of ane-mail message that uses a custom form. The e-mail message 2300 includesthree fields that have been added by the sender of the message. Thesefields are a “Length” field 2305, a “Width” field 2310, and a “Height”field 2315. It will be understood that these fields have been added to aconventional e-mail message in accordance with the preferred e-mailsystem. The present invention is not limited to the addition of thesefields to an e-mail message, but can be extended to the addition of more(or fewer) custom fields. In addition, the present invention may be usedto simply rearrange the fields of a conventional e-mail message withoutadding any fields. Those skilled in the art will appreciate that thedata entered in these fields is stored as a value in the correspondingproperties of the e-mail message item (FIG. 19).

[0215] Thus, from the foregoing description, it will be obvious to thoseskilled in the art that the present invention provides a method forcreating and sending an e-mail message that includes a custom form. Thedata corresponding to the custom form is stored in a property of thee-mail message item along with the other properties of the message. Thecustom form does not need to be installed on a memory storage device orstored in a form registry provider 500 (FIG. 5j before being used.

[0216] Having described the method for creating and sending an e-mailmessage that includes a custom form, a description of the method forreceiving a message with a custom form will now be presented. When thepreferred e-mail program module is used to open a message that has beenreceived, the module determines whether the message item has a “form”property. If the message item has a “form” property, the layoutinformation, stored as a value in the “form” property, is read and usedto view the contents of the e-mail message. If the message item does nothave a “form” property, then the layout information is read from theMAPI form registry provider 500 (FIG. 5) and the message item isdisplayed. The only action performed by a recipient is to open thee-mail message. The e-mail program module will determine where to findthe form and will extract the layout information from the appropriatesource.

[0217]FIG. 24 is a flow diagram of the steps performed by a recipient'scomputer in displaying a received message item. The method 2400 beginsat start step 2402 and proceeds to step 2405 when the computer receivesa command from the user to open a message item in the user's inbox.After the computer receives a command to open a message item, thecomputer proceeds to step 2410 to determine whether the message itemincludes a “form” property. If not, the computer proceeds to step 2415and selects the appropriate form layout information, of form data, fromthe form registry provider. After extracting the layout information fromthe form registry provider, the computer combines the data from themessage item with the layout information from the form registry providerand displays the message at step 2420. The display of the messageincludes display of the fields and the field data in the fields. Asthose skilled in the art will understand, the field data is stored asvalues in properties in the message item. When displaying a messageitem, the value in a property is extracted and displayed in thecorresponding field. At step 2425, the method ends.

[0218] Returning to step 2410, if the computer finds a “form” propertyin the message item, then the computer proceeds to step 2430. At step2430, the computer extracts the value, or layout information, stored inthe “form” property of the message item. As will be apparent to thoseskilled in the art, the layout information is the binary data, or value,that is stored in the “form” property. Using this layout information,the computer combines the data from the message item with the displayinformation in the message's “form” property and displays the messageitem at step 2420. At step 2425, the method ends.

[0219] The information that is displayed to the recipient of an e-mailmessage that uses a custom form, i.e., the “read” page, is preferablythe same as the information that is displayed to the designer of themessage, i.e., the “compose” page. For example, the e-mail message 2300in FIG. 23 includes three fields that were added by the sender of themessage. The display illustrated in FIG. 23 is the “compose” page. Thee-mail message displayed to the recipient, the “read” page, of themessage in FIG. 23 preferably has the same information and arrangementas the “compose” page. Thus, a recipient of an e-mail message that usesa custom form does not need to install the custom form before openingthe message. In addition, as further described below, the presentinvention provides a method for responding to an e-mail message thatuses a custom form.

[0220] Those skilled in the art will appreciate that when a recipient ofan e-mail message with a custom form replies to the message, the “form”property and its associated fields are used in the reply message. Whencomposing the reply, the user may alter the data in the fields thatconstitute the custom form, in which case the new data is stored in theproperties associated with those fields. Furthermore, the user mayfurther customize the form by selecting the “design form” option. Inthis case, data corresponding to the layout of the newly customized formis stored in the e-mail message's form property. When the reply is sent,the transmitted message item includes the form property and propertiescorresponding to the constituent data. Thus, the process of replying toa message is substantially similar to the process described inconjunction with FIGS. 20 and 22.

[0221] As mentioned above, the “read” page and “compose” page of acustom form are preferably displayed the same. However, an embodiment ofthe present invention allows the designer of a custom form to design the“read” and “compose” pages to be displayed differently from one another.For example, the “compose” page in FIG. 23 has explicit fields, a“Length” field 2305, a “Width” field 2310, and a “Height” field 2315.The “read” page of a message using a form with these fields may bedesigned to be displayed as in FIG. 25. The “read” page of the message2500 in FIG. 25 displays only a “dimensions” field 2505, which combinesthe data from the “Length” field, the “Width” field, and the “Height”field. Thus, the designer of a custom form can design the “read” page todisplay differently than the “compose” page. In addition, the designerof a custom form may also design a form such that certain fields may notbe changed in the “read” page.

[0222] From the foregoing description, those skilled in the art willappreciate that the present invention facilitates communication betweene-mail users by allowing users to create, use and share custom formsspontaneously without requiring publication or installation on otherusers' computers. This allows small work groups to develop their owntools without requiring company-wide publication of forms.

[0223] The Preferred Method for Tallying E-mail Responses

[0224] E-mail systems provide an effective means of communicating with alarge number of individuals in an organization, such as by sending asingle e-mail message to a number of different individuals. Many times,an e-mail message is sent to a number of individuals in order to solicita response to a particular query. For example, an office administratormay send an e-mail message to all of the employees in an office asking,“Will you attend the office breakfast?” As another example, an e-mailuser may send an e-mail message to his or her co-workers listing severalrestaurants and asking, “At which restaurant would you like theChristmas party held?”

[0225] Although prior art e-mail systems make it easy to ask a questionof a group of people, the prior art has not provided any convenient oreffective way for the sender to organize the responses once they arereceived. The present invention allows a sender of an e-mail message tocreate an “autoresponse message” with “voting buttons,” which correspondto possible responses to the question addressed in the e-mail message.When each recipient opens the autoresponse message, he sees the questionin the body or subject field of the e-mail message and a command barwith voting buttons at the top of the message. To respond, the recipientselects one of the voting buttons in the command bar, edits the reply(if desired), and sends the reply. When the sender's e-mail programreceives an autoresponse reply from a recipient, the reply is recognizedas an autoresponse reply and the recipient's vote is tallied in thesender's copy of the original message, which is referred to as the “sentmail copy.” When the sender opens his or her sent mail copy of theoriginal autoresponse message, he or she is able to view a list thatincludes the name of each recipient, their response, the time of theirresponse, and a tally of the voting results.

[0226] As mentioned earlier, an e-mail message, or e-mail item, includesa plurality of properties. Each property includes a property tag andvalue which are stored together in system memory 15 (FIG. 1) as a singledata structure. In most cases, the properties correspond to a field thatis displayed. FIG. 26 illustrates an e-mail message item 2600 thatincludes a plurality of properties. These include the standardproperties, such as a “sender” property 2605, a “recipient(s)” property2610, a “subject” property 2615, and a “body” property 2620. When ane-mail message is transmitted to the recipient, the property tags andvalues are transmitted to the recipient via a network.

[0227] Message items also typically contain a property or propertiesused by the e-mail program module to track whether an e-mail item hasbeen sent, received, read, etc. These properties are usually notdisplayed to the user. An example of such a property is the MAPIproperty PR_REPORT_TAG. The value stored in a PR_REPORT_TAG property isknown as a moniker. The moniker contains data identifying the messagestore in which the sent mail copy of a message was stored. The monikeralso contains data identifying the folder in which the sent mail copy ofthe message was stored when the original message was sent. The monikerfurther contains a search key number, which is a unique number thatidentifies the sent mail copy of the message. Thus, the moniker allowsan e-mail program module to locate the sent mail copy of an e-mailmessage, so that it can be updated when the original message has beensent, received, read, etc.

[0228] As illustrated in FIG. 26, the preferred e-mail module usesadditional properties to provide the autoresponse feature. Theadditional properties include a “my vote” property 2625, an“autoresponse verbs” property 2630, a “PR_REPORT_TAG” property 2635, andat least one “voter” property 2640, which correspond to the names of therecipients 2645 of the e-mail message.

[0229] The “autoresponse verbs” property 2630 has a value thatcorresponds to the possible responses, or choices, that can be sent inreply to an autoresponse message query. For example, as shown in FIG.26, if an autoresponse message includes the query “At which restaurantwould you like the Christmas party held?” and the possible choices ofrestaurants are Chez Jean, Mama Rosa's, and Big Bob's, then the valuestored in the “autoresponse verbs” property is “Chez Jean, Mama Rosa's,Big Bob's.”

[0230] The “my vote” property 2625 is a property with a valuecorresponding to the vote of the recipient. The value associated withthe “my vote” property is empty in the original autoresponse messageitem. When the recipient enters their vote, an autoresponse verb isexecuted as will be further described below. One of the actionsassociated with an autoresponse verb is to store the name of theautoresponse verb as the value of the “my vote” property in theautoresponse reply message.

[0231] “Recipient name” properties 2640 corresponding to the name ofeach recipient 2645 are also used to implement the autoresponse feature.The value of each “voter” property is empty in an autoresponse messageitem and in an autoresponse reply. Each autoresponse reply message isused to update the sent mail copy of the autoresponse message. The valuecorresponding to the “my vote” property in the autoresponse replymessage is stored in the “voter” property of the sent mail copy of theautoresponse message. For example, when Jim receives an autoresponsemessage, he selects one of the voting buttons to enter his vote. Thedata corresponding to Jim's vote is stored as the value in the “my vote”property of Jim's autoresponse reply message. When Jim's autoresponsereply message is received by the e-mail program module of the sender ofthe original autoresponse message, the sent mail copy of theautoresponse message will be updated to reflect Jim's vote.Specifically, the “voter” property, “Jim,” in the sent mail copy of theautoresponse message is updated to reflect the same value as the “myvote” property in the autoresponse reply from Jim.

[0232] Having described the additional properties employed by thepreferred e-mail module to implement the autoresponse feature, we turnnow to the e-mail form used to execute the autoresponse feature. Asdescribed above in the section entitled “The Messaging ApplicationProgramming Interface (MAPI),” a form is a viewer for a message. Clientapplication developers can create custom forms. These custom formsimplement a set of standard menu commands (such as open, create, deleteand reply) and a set of commands specific to that particular form.

[0233] The commands implemented by a form are also known as verbs. A setof actions, or steps, is performed when a verb is selected by a user ofan e-mail program module. As an example, when a user of an e-mailprogram module selects the reply verb or command, several actionstypically occur: (1) the value of the recipient property in the originalmessage is stored as the value of the sender property in the replymessage; (2) the value of the sender property in the original message isstored as the value of the recipient property in the reply message; (3)the characters “Re:” are added to the value of the subject property inthe original message, and this combined data is stored is stored in thesubject property in the reply message, and (4) the value of the bodyproperty in the original message is stored as the value of the bodyproperty in the reply message.

[0234] The preferred e-mail program module uses a custom form and customverbs to implement the autoresponse feature. The custom form includescustom verbs known as autoresponse verbs. As mentioned above, eachautoresponse verb corresponds to a voting button. When a voting buttonis selected by a recipient of an autoresponse message, the autoresponseverb associated with that voting button is executed. Each autoresponseverb executes the same three actions: (1) an autoresponse reply messageitem is created; (2) the name of the autoresponse verb that was executedis stored as the value of the “my vote” property of the reply; and (3)the name of the autoresponse verb is stored, along with the value of the“subject” property of the original message, as the value of the“subject” property of the reply.

[0235] Having presented a basic overview of properties, forms, andfields, a detailed description of the steps performed by a user tocreate an autoresponse e-mail message will be presented below.

[0236]FIG. 27 is a flow diagram that illustrates the steps performed bya user to create an autoresponse e-mail message. Although the method ofcreating, sending, and replying to an autoresponse e-mail message isdescribed below in the context of a user executing certain steps and acomputer performing certain steps, those skilled in the art willunderstand that the present invention is a computer-implemented processcarried out by a computer in response to both user input andinstructions from an e-mail program module.

[0237] The method 2700 begins at start step 2702 and proceeds to step2705 when the user decides to create a new e-mail message. At step 2705,the user performs the steps associated with the creation of aconventional e-mail message, including identifying the recipients of themessage, entering a subject, and typing in the text of the message.

[0238] At step 2710, the user decides whether to activate theautoresponse feature. If the user decides not to activate autoresponse,then the user proceeds to step 2715 and sends the e-mail message. Afterthe message is sent, the method 2700 ends at step 2720.

[0239] If, at step 2710, the user decides to activate autoresponse, theuser proceeds to step 2725, activates the autoresponse feature, andenters a set of possible responses to the query presented in themessage. Referring now to FIG. 28, activating the autoresponse featureis preferably accomplished by selecting an options page 2805 of thee-mail program module and clicking a “use voting buttons” checkbox 2810.In the preferred e-mail program module, this results in the display ofan entry blank 2815 and a drop-down menu 2820. The user then may entereach possible predefined response, separated by a semicolon, into thedisplayed entry blank. Each possible response entered by the user isknown as a token. For example, if the query posed in the e-mail messageis “At which restaurant would you like the Christmas party held?,” theuser might enter the tokens 2825 by typing in the names of severaldifferent restaurants, such as Chez Jean;Mama Rosa's;Big Bob's as shownin FIG. 28. As mentioned above, the preferred application program alsodisplays a drop-down menu 2820 when the “use voting buttons” checkbox isselected. The drop-down menu includes pre-defined token sets 2830. Thepre-defined token sets are combinations of tokens that are frequentlyused, such as Approve; Reject, Yes; No, and Yes;No;Maybe. Thus, when auser needs to use one of the pre-defined token sets 2830, the userselects the pre-defined token set in the drop-down menu rather thanentering the tokens into the entry blank.

[0240] Returning to FIG. 27, after the user enters the tokens at step2725, the user proceeds to step 2715 and sends the e-mail message.Therefore, to create an autoresponse message, the user creates an e-mailmessage, activates the autoresponse feature, enters tokens, and sendsthe autoresponse message. The functions performed by the computer of thesender of an autoresponse message are described below in reference toFIG. 29.

[0241]FIG. 29 is a state diagram illustrating the functions performed bya computer that is being used to create an e-mail message that includesthe autoresponse feature. The method 2900 begins at state 2905 with thecomputer in an idle state as it relates to instructions provided by thee-mail program module. When the user selects the command for creating anew message, the computer proceeds to state 2910, where it receives theinformation that is typically associated with a conventional e-mailmessage. This includes receiving data indicative of the recipients,subject, priority, and body, and storing this data as values in thecorresponding properties that constitute the message item. If the userthen selects the “send” command, the computer proceeds to state 2915 andtransmits the e-mail message item. After the message is sent, thecomputer returns to the idle state 2905.

[0242] Referring again to state 2910, if the user selects the optionspage and clicks a “use voting buttons” checkbox, the computer proceedsto state 2920. At state 2920, the computer adds the autoresponseproperties to the message item. As mentioned above, the creation of newmessage properties is facilitated by the MAPI function SetProps. To addthe “autoresponse verbs” property, the computer receives a set of tokensentered by the user. The computer creates a custom verb from each tokenand stores the data indicative of the name of each verb as the value ofthe “autoresponse verbs” property.

[0243] At state 2920, the computer also adds a “my vote” property and“voter” properties corresponding to the names of each of the recipientsto the message item. The “my vote” property and the “voter” propertiesdo not have any data stored as their value when they are added to theautoresponse message. At state 2920, the computer also stores a monikerin the PR_REPORT_TAG property.

[0244] When the user selects the “send” command, the computer proceedsto state 2915 and transmits the autoresponse message item. The computeralso stores a sent mail copy of the autoresponse message. The sent mailcopy is preferably stored in the sender's sent mail folder, but the sentmail copy may be stored in another memory storage location specified bythe sender. The sent mail copy of the autoresponse message will beupdated when recipients reply to the autoresponse message. This updatingwill be described below in reference to FIG. 34.

[0245] Turning now to the process of receiving an autoresponse message,FIG. 30 is a flow diagram that illustrates the steps that may beperformed by a recipient of an autoresponse message. The method 3000begins at start step 3002 and proceeds to step 3005 when the user opensan e-mail message item with the autoresponse feature. After opening themessage, the user may read the text of the message, including the querypresented by the sender of the autoresponse message. For example, in thepreferred application program, the user, after opening an autoresponsemessage, views a message 3100 such as is shown in FIG. 31. Theautoresponse message is similar to a conventional e-mail message andincludes a “from” field 3105, an address field 3110, a “Cc” field 3115,a “subject” field 3120, and a “body” field 3125. The autoresponsemessage also includes the voting buttons 3130.

[0246] Referring again to FIG. 30, after the user has opened and viewedthe message at step 3005, the user selects one of the voting buttons atstep 3010. When the user selects one of the voting buttons, an alert boxmessage will appear that will warn the user that their reply will now besent. The alert box message asks the user if he would like to edit thereply before sending the reply message. At step 3015, the user decideswhether to edit his reply before sending the message. If the userdecides not to edit his reply, then the user clicks the “send” button atstep 3020. The method ends at step 3025.

[0247] Returning to step 3015, if the user decides to edit his response,then the user enters data into the body field of the autoresponse replyat step 3030. When the user decides to send the autoresponse replymessage, the user proceeds to step 3020 and sends the message. Themethod ends at step 3025.

[0248] Therefore, a recipient of an autoresponse message needs only toexecute a few simple steps to reply to an autoresponse message. Therecipient opens the autoresponse message, reads the query presented inthe message, selects a voting button, edits the reply (if necessary),and sends the autoresponse reply to the sender. The functions performedby a computer of a recipient who is replying to an autoresponse messageare described below.

[0249]FIG. 32 is a state diagram illustrating the functions performed bya computer that is being used to open and reply to an autoresponsee-mail message. The method 3200 begins at step 3205 with the computer inan idle state as it relates to instructions provided by the e-mailprogram module. If the user invokes an “open message” command, thecomputer goes to state 3210 and opens the selected autoresponse message.The computer searches the message item to locate the “autoresponseverbs” property. As described above, the responses, or tokens, enteredby the sender of the message are used to create “autoresponse verbs.”The data indicative of the names of these autoresponse verbs are storedis stored as a value in a property called autoresponse verbs. Thecomputer reads the value of the “autoresponse verbs” property anddisplays voting buttons corresponding to each autoresponse verb.

[0250] If the user selects a voting button, then the computer proceedsto state 3215. At state 3215, the computer executes the “autoresponseverb” corresponding to the voting button. As described above, when anautoresponse verb is executed, the computer stores the datacorresponding to the name of the autoresponse verb chosen by therecipient as the value in the “subject” property of the reply message.The computer also stores the data corresponding to the name of theautoresponse verb selected by the recipient as the value in the “myvote” property of the reply message. Also, the PR_REPORT_TAG propertyassociated with the original message is copied by the computer into thereply message.

[0251] Returning to state 3215, if the user decides to send theautoresponse reply message without editing, then the computer proceedsto state 3220 and transmits the autoresponse reply. The computer thenreturns to the idle state 3205.

[0252] If the user does decide to edit the reply message, then thecomputer proceeds to state 3225. At state 3225, the computer receivesdata indicative of changes to the fields of the message and stores thisdata as the value of the corresponding property in the message item.When the user sends the message, the computer proceeds to state 3220 andtransmits the message.

[0253] When an autoresponse reply is sent back to the original sender ofthe autoresponse message, the reply is processed, i.e., the votingresults are updated, when the reply message is opened for the firsttime. The reply may be opened in a conventional manner by the userselecting an open command for the autoresponse reply. The autoresponsereply may also be processed in the background, i.e., without any inputfrom the user, by an automatic processor known as a sniffer. The snifferensures that autoresponse replies are processed in a timely manner evenif the user never opens the replies. FIG. 33 is a flow diagramillustrating the functions performed by the sniffer when an autoresponsereply is received. The method 3300 begins at step 3305. The snifferdetermines at step 3305 whether the computer is idle. If the computer isidle, the sniffer proceeds to step 3310 to determine whether there is amessage to sniff. This is preferably done by searching a “sniff state”property that is associated with unread messages. The “sniff state”property can have three values: “none,” “on sniff,” or “on open only.”If the “sniff state” property is “on stiff,” then the message isprocessed by the sniffer. If the “sniff state” property is “none” or “onopen only,” the sniffer returns to step 3305 to determine whether thecomputer is still idle.

[0254] Returning to step 3310, if the sniffer finds a message with avalue of “on sniff” in its “sniff state” property, the sniffer proceedsto step 3315 and processes the autoresponse response message item. Afterprocessing the autoresponse response message item at step 3315, thesniffer closes the autoresponse response message item at step 3320. Thesniffer then proceeds to step 3305 to determine whether the computer isstill idle.

[0255] Thus, those skilled in the art will recognize that the snifferwill process an autoresponse reply message item even if the originalsender never opens the reply. In addition, an autoresponse reply messageitem will be processed even if the user deletes the message item beforethe sniffer is able to process the message item. When a user deletes theautoresponse reply message item, the original message will be updated toreflect the content of the reply before the message item is deleted.Because of these features, the user does not have to open each and everyresponse to tally results. Instead, the user may simply open the “sentmail” copy of the autoresponse message to view the voting results.

[0256]FIG. 34 is a state diagram illustrating the functions performed bya computer that is being used to update the sent mail copy of anautoresponse message. The method 3400 begins at step 3405 with thecomputer in an idle state as it relates to instructions provided by thee-mail program module. When the user selects the command to open anautoresponse response item or the sniffer opens an autoresponse responseitem, the computer proceeds to state 3410. The computer reads the valueof the PR_REPORT_TAG property of the autoresponse response in state3410. The value of the PR_REPORT_TAG is known as a moniker. The monikercontains information used to locate the original autoresponse message onthe sender's computer. The original autoresponse message must be foundto update the original message with the votes of the recipients.Specifically, the moniker contains data corresponding to the messagestore that the original message was stored in, the folder that theoriginal message was stored in, and a search key. Returning to step3410, the computer reads the moniker and searches the computer's memorystorage devices for a message store that corresponds to the messagestore identified in the moniker.

[0257] Once the computer finds the proper message store, the computerproceeds to step 3415. At step 3415, the computer searches the messagestore for a folder that corresponds to the folder identified in themoniker. After the proper folder is found, the computer proceeds to step3420. At step 3420, the computer opens the folder and searches for amessage with a search key corresponding to the search key identified inthe moniker. The message with the corresponding search key is theoriginal autoresponse message. After the original autoresponse messageis found, the computer proceeds to step 3425. It will be appreciatedthat, at any point in the process of finding the original message, theprocess could terminate if the proper message store, proper folder, orproper message is not found.

[0258] At step 3425, the computer opens the original autoresponsemessage and searches for a “voter” property corresponding to the valueof the “sender” property of the autoresponse reply. For example, if Bobreceives an original autoresponse message and responds by selecting avoting button, then the autoresponse reply from Bob will contain dataindicative of “Bob” in the “sender” property. When the autoresponsereply is opened, the computer finds the original autoresponse message asdescribed above in reference to states 3410-3420. The computer thenopens the original autoresponse message and searches for the “voter”property corresponding to “Bob.”

[0259] After the “voter” property is found at state 3425, the computerproceeds to step 3430. The computer updates the value of the “voter”property with the value of the “my vote” property of the autoresponsereply. After the sniffer or the user closes the autoresponse reply, thenthe computer returns to idle state 3405.

[0260] When a sender of an autoresponse message wants to view thereplies to his or her message, the sender may view each individual replyto the autoresponse message. For example, FIG. 35 illustrates the inbox3500 of a e-mail program module in a list view. Message 3505 and message3510 are autoresponse reply messages. The name of the autoresponse verb3515 chosen by the recipient 3520 of the autoresponse message is listedunder the subject heading of the inbox before the original subject ofthe autoresponse message. It will be understood that including therecipient's “vote” in the subject of the message provides a distinctadvantage over the prior art. The user does not need to open theresponse in order to read the vote of the recipient because it isalready listed in the subject heading. Furthermore, it will be apparentthat the sender of the autoresponse message can open the individualreply messages and read the vote of the recipient and any comments therecipients may have edited into their reply. However, because of thesniffer, the sender of an autoresponse message does not have to openeach individual reply message to tally the results since the snifferwill process the replies in the background.

[0261] In addition to viewing the inbox, the sender of an autoresponsemessage can open his or her sent mail copy of the autoresponse message.When the sender opens the sent mail copy of the autoresponse message, heviews a list of the recipients 3605, their responses 3610, the time 3615each response was received, and a current tally 3620 of the vote resultssuch as is illustrated in FIG. 36.

[0262] As known to those skilled in the art, the current tally for eachvote is found by computing the number of recipients that have respondedwith that vote.

[0263] In another embodiment, when the sender opens a reply to theautoresponse message, the computer displays a list of the results suchas is shown in FIG. 36. Thus, in this embodiment, the sender can viewthe results by opening any reply message rather than locating andopening the sent mail copy of the autoresponse message.

[0264] From the foregoing description, those skilled in the art willappreciate that autoresponse messages facilitate communication betweenthe sender of an e-mail message containing a query and the recipients ofthe e-mail query. This is accomplished by allowing the sender of thee-mail message to add voting buttons that correspond to the possibleresponses to the e-mail query. To reply, each recipient simply selects avoting button and sends their reply. When the replies are received atthe sender's e-mail program module, the votes are automatically talliedby a background process, known as a sniffer, or when the sender opens areply. However, because of the automatic processing of the sniffer, thesender does not have to open every e-mail reply to see the votingresults. Instead, the sender simply opens a sent mail copy of the e-mailquery to view the voting results. When the sent mail copy is opened, thesender may view a list of the recipients, their response, the time theirresponse was received, and a current tally of the voting results.

[0265] Summary of the Detailed Description

[0266] From the foregoing description, it will be appreciated that thepresent invention provides an improved system and method for processingand organizing e-mail message items. The preferred system and method areembodied in an e-mail module that forms a part of a personal informationmanager program. In summary, recipient names are resolved in thebackground while the user composes the remainder of the message.Unambiguous names are resolved without further intervention by the user.The user resolves ambiguous names by selecting from a list of possiblematches displayed in a context menu. The e-mail module remembers howambiguous names are resolved and automatically creates nicknames forfuture use. In addition to a subject and body, each e-mail message maycontain a message flag, which specifically identifies follow-up actionsthat need to be performed and deadlines for those actions. The messageflag and due date are stored in message properties and may be edited byeither the sender or the recipient. The message flags allow a recipientto quickly determine which messages have action items associated withthem, when they are due, and whether they have been completed. Anotheraspect of the present invention allows users to create and share custome-mail forms. The attributes of the custom form are stored in an e-mailproperty, along with the data that will be displayed in the custom form.Finally, another aspect of the present invention allows E-mail users tosolicit input from a group of recipients by providing predeterminedchoices for their response. Each recipient replies to the original queryby selecting a response. When the sender receives the replies, theresponse is automatically tallied and easily available to the sender.

[0267] The foregoing system may conveniently be implemented in a programmodule or program that is based upon the flow charts and state diagramsin FIGS. 9, 10, 13, 16, 17 18, 22, 24, 29, 32, 33 and 34. No particularprogramming language has been described for carrying out the variousprocedures described above because it is considered that the operations,steps, and procedures described above and illustrated in theaccompanying drawings are sufficiently disclosed to permit one ofordinary skill in the art to practice the present invention. Moreover,there are many computers and operating systems which may be used inpracticing the present invention and therefore no detailed computerprogram could be provided which would be applicable to all of these manydifferent systems. Each user of a particular computer will be aware ofthe language and tools which are most useful for that user's needs andpurposes.

[0268] The present invention has been described in relation toparticular embodiments which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those skilled in the art to which the presentinvention pertains without departing from its spirit and scope.Accordingly, the scope of the present invention is defined by theappended claims rather than the foregoing description.

What is claimed is:
 1. In an electronic mail system, a method forresolving a display name associated with an intended recipient of amessage item, comprising the steps of: receiving in an address fieldsaid display name; determining whether said display name uniquelymatches one of a plurality of registered users of said electronic mailsystem; and in response to said display name uniquely matching one ofsaid registered users, displaying in said address field recipient datacorresponding to said matching registered user, otherwise, displayingambiguous address data in said address field.
 2. The method recited inclaim 1, wherein said ambiguous address data comprises said display nameand predetermined indicia.
 3. The method recited in claim 1, whereinrecipient data corresponding to said matching registered user comprisesat least a portion of a name of said matching registered user.
 4. Themethod recited in claim 1, wherein said step of determining whether saiddisplay name uniquely matches one of a plurality of registered users isprocessed while a user composes the remainder of said message item. 5.The method recited in claim 1, further comprising the steps of:receiving in said address field first user input corresponding to saidambiguous address data; displaying, in response to said first userinput, a list of registered users corresponding to said ambiguousaddress data; receiving second user input corresponding to a selectedone of said displayed list of registered users; and in response to saidsecond user input, displaying in said address field recipient datacorresponding to said selected registered user.
 6. The method recited inclaim 5, further comprising the step of creating a nickname entrycharacterized by said display name being associated with said selectedregistered user.
 7. In an electronic mail system, a method for usingnicknames to resolve the name of an intended recipient of a messageitem, comprising the steps of: receiving in an address field a displayname associated with said intended recipient; determining whether saiddisplay name corresponds to a previously stored nickname; in response tosaid display name corresponding to said previously stored nickname,displaying in said address field nickname data corresponding to aregistered user of said electronic mail system associated with saidpreviously stored nickname; otherwise, determining whether said displayname uniquely matches one of a plurality of registered users of saidelectronic mail system; and in response to said display name uniquelymatching one of said registered users, displaying in said address fieldrecipient data corresponding to said matching registered user,otherwise, displaying ambiguous address data in said address field. 8.The method as recited in claim 7, wherein said ambiguous address datacomprises said display name and predetermined indicia.
 9. The method asrecited in claim 7, wherein said nickname data comprises at least aportion of a name of said registered user and predetermined indicia. 10.The method as recited in claim 7, wherein recipient data correspondingto said matching registered user comprises at least a portion of a nameof said matching registered user.
 11. The method as recited in claim 7,wherein said steps of determining whether said display name correspondsto a previously stored nickname and determining whether said displayname uniquely matches one of a plurality of registered users areperformed while a user composes the remainder of said message.
 12. Themethod as recited in claim 7, further comprising the steps of: receivingin said address field first user input corresponding to said ambiguousaddress data; displaying, in response to said first user input, a listof registered users corresponding to said ambiguous address data;receiving second user input corresponding to a selected one of saiddisplayed list of registered users; and in response to said second userinput, displaying in said address field recipient data corresponding tosaid selected registered user.
 13. The method as recited in claim 12,further comprising the step of creating a nickname entry characterizedby said display name being associated with said selected registereduser.
 14. The method as recited in claim 7, further comprising the stepsof: receiving in said address field first user input corresponding tosaid nickname data; displaying, in response to said first user input, alist of registered users corresponding to said nickname data; receivingsecond user input corresponding to a selected one of said displayed listof registered users; and in response to said second user input,displaying in said address field recipient data corresponding to saidselected registered user.
 15. The method as recited in claim 14, furthercomprising the step of updating a nickname entry in which said displayname is stored in association with said selected registered user.
 16. Acomputer system for using nicknames to resolve the name of an intendedrecipient of a message item, comprising: a central processing unit(CPU); an input device connected to said CPU; a display device coupledto said CPU; and memory coupled to said CPU for storing a programmodule; said CPU, responsive to instructions from said program module,being operative to: receive from said input device a display nameindicative of said intended recipient, said display name being enteredin an address field displayed on said display device; determine whethersaid display name corresponds to a previously stored nickname; inresponse to said display name corresponding to said previously storednickname, display in said address field nickname data corresponding to aregistered user associated with said nickname; otherwise, determinewhether said display name uniquely matches one of a plurality ofregistered users of said electronic mail system; and in response to saiddisplay name uniquely matching one of said registered users, display insaid address field recipient data corresponding to said matchingregistered user, otherwise, display ambiguous address data in saidaddress field.
 17. The computer system recited in claim 16, wherein saidambiguous address data comprises said display name and predeterminedindicia.
 18. The computer system recited in claim 16, wherein saidnickname data comprises at least a portion of a name of said registereduse and predetermined indicia.
 19. The computer system recited in claim16, wherein recipient data corresponding to said matching registereduser comprises at least a portion of a name of said matching registereduser.
 20. The computer system recited in claim 16, wherein said CPU isfurther operative to: receive in said address field first user inputcorresponding to said ambiguous address data; display, in response tosaid first user input, a list of registered users corresponding to saidambiguous address data; receive second user input corresponding to aselected one of said displayed list of registered users; and in responseto said second user input, display in said address field recipient datacorresponding to said selected registered user.
 21. The computer systemrecited in claim 20, wherein said CPU is further operative to create anickname entry characterized by said display name being associated withsaid selected registered user.
 22. The computer system recited in claim16, wherein said CPU is further operative to: receive in said addressfield first user input corresponding to said nickname data; display, inresponse to said first user input, a list of registered userscorresponding to said nickname data; receive second user inputcorresponding to a selected one of said displayed list of registeredusers; and in response to said second user input, display in saidaddress field recipient data corresponding to said selected registereduser.
 23. The computer system recited in claim 22, wherein said CPU isfurther operative to update a nickname entry in which said display nameis stored in association with said selected registered user.
 24. Acomputer-readable medium on which is stored a computer program forresolving a display name associated with an intended recipient of amessage item, said computer program comprising instructions which, whenexecuted by a computer, perform the steps of: receiving in an addressfield said display name; determining whether said display name uniquelymatches one of a plurality of registered users of said electronic mailsystem; in response to said display name uniquely matching one of saidregistered users, displaying in said address field recipient datacorresponding to said matching registered user; and otherwise,displaying ambiguous address data in said address field.
 25. Thecomputer-readable medium recited in claim 24, wherein said ambiguousaddress data comprises said display name and predetermined indicia. 26.The computer-readable medium recited in claim 24, wherein recipient datacorresponding to said matching registered user comprises at least aportion of a name of said matching registered user.
 27. Thecomputer-readable medium recited in claim 24, further comprising thesteps of: receiving in said address field first user input correspondingto said ambiguous address data; displaying, in response to said firstuser input, a list of registered users corresponding to said ambiguousaddress data; receiving second user input corresponding to a selectedone of said displayed list of registered users; and in response to saidsecond user input, displaying in said address field recipient datacorresponding to said selected registered user.
 28. Thecomputer-readable medium recited in claim 27, further comprising thestep of creating a nickname entry characterized by said address databeing associated with said selected registered user.
 29. In anelectronic mail system for transmitting a message item, said messageitem including a plurality of properties, a method for including a flagwith said message item, comprising the steps of: receiving flag dataindicative of said flag; storing said flag data as one of said pluralityof properties; and transmitting said message item to a recipient viasaid electronic mail system.
 30. The method recited in claim 29, whereinsaid flag data identifies a follow-up action associated with saidmessage item, and further comprising the steps of: receiving due datedata indicative a date by which said follow-up action is to beperformed; and storing said due date data as one of said plurality ofproperties.
 31. The method recited in claim 29, wherein said pluralityof properties includes a status property indicative of whether saidmessage item includes flag data.
 32. The method recited in claim 29,wherein said flag data includes text representing an instruction to therecipient of said message item.
 33. In an electronic mail system forreceiving message items, said message items including a plurality ofproperties, a method for displaying the status of a follow-up actionassociated with said message items, comprising the steps of: receivingone of said message items, said message item including a status propertyassociated with said follow-up action; determining whether said messageitem includes said status property; in response to a determination thatsaid message item includes said status property, retrieving status datastored with said status property; and displaying said status data inconjunction with said message item.
 34. The method recited in claim 33,wherein said displayed status data indicates whether said message itemincludes a follow-up action.
 35. The method recited in claim 34, whereinsaid displayed status data indicates whether said follow-up action iscomplete.
 36. The method recited in claim 33, wherein said status dataincludes text and is displayed in conjunction other text associated withsaid message item.
 37. The method recited in claim 33, furthercomprising the steps of: receiving a plurality of said message items;and sorting said message items according to data included in said statusproperty.
 38. In an electronic mail system for receiving message items,said message items including a plurality of properties, a method forproviding an indication corresponding to due date associated with saidmessage item, comprising the steps of: receiving one of said messageitems, said message item including a due date property; retrieving duedate data from said due date property; comparing said due date data tothe current time; and displaying an indication corresponding to therelationship between said due date data and the current time.
 39. Themethod recited in claim 38, wherein said indication indicates that saiddue date is past due.
 40. The method recited in claim 38, wherein saidindication is an alarm indicating that said due date will occur within apredetermined period of time.
 41. In an improved message item fortransmission in an electronic mail system, the improvement comprising: amessage flag property including message flag data indicative of afollow-up action associated with said message item; and a statusproperty including status data indicative of whether said follow-upaction has been completed by a recipient of said message item.
 42. Theimprovement recited in claim 41, further comprising a due date propertyincluding due date data indicative of a time by which said follow-upaction should be completed.
 43. A computer-readable medium on which isstored a computer program for indicating a follow-up action associatedwith a message item, said computer program comprising instructionswhich, when executed by a computer, perform the steps of: adding amessage flag property to said message item; receiving message flag dataindicative of said follow-up action; storing said message flag data insaid message flag property; and transmitting said message item to arecipient via an electronic mail system.
 44. The computer readablemedium recited in claim 43, wherein said steps performed by saidcomputer further comprise: adding a due date property to said messageitem; receiving due date data indicative a date by which said follow-upaction is to be performed; and storing said due date data in said duedate property.
 45. The computer readable medium recited in claim 43,wherein said message item further comprises a status property indicativeof whether said message flag property includes message flag data.
 46. Inan electronic mail system for transmitting an item, said item includinga plurality of properties, a method for transmitting custom form data aspart of said item, comprising the steps of: obtaining said custom formdata, said custom form data indicative of the layout of a custom formcomprising a plurality of fields for displaying field data stored in atleast one of said plurality of properties; storing said custom form datain one of said plurality of properties in response to obtaining saidcustom form data; and transmitting said item to a recipient.
 47. Themethod of claim 46, further comprising the steps of: receiving saidfield data from said fields as input; and storing said field data insaid at least one of said plurality of properties.
 48. The method ofclaim 46, wherein said step of obtaining said custom form data comprisesthe steps of: displaying a form; altering said form in response toinput; and creating said custom form data corresponding to said alteredform.
 49. In an electronic mail system for receiving an item, a methodfor displaying an item comprising the steps of: receiving said item,said item including a plurality of properties; determining whether saiditem includes a form property; in response to a determination that saidmessage item includes said form property, retrieving form data stored insaid form property; otherwise, retrieving form data from a formregistry; and displaying said item in the context of a form, said formbeing defined by said form data.
 50. The method of claim 49, whereinsaid form data defines the layout of a plurality of fields of said form,and wherein information is displayed in said fields, said informationbeing stored in at least one of said plurality of properties.
 51. Themethod of claim 49, wherein said form registry comprises data stored ona memory storage device, said data corresponding to a description of atleast one form.
 52. The method of claim 49, wherein said form propertycomprises data corresponding to a description of said form.
 53. Acomputer-readable medium on which is stored a computer program fortransmitting custom form data as part of an item, said computer programcomprising instructions which, when executed by a computer, perform thesteps of: adding a form property to said item; obtaining said customform data, said custom form data indicative of the layout of a customform comprising a plurality of fields for displaying field data storedin at least one of a plurality of properties; storing said custom formdata in said form property in response to obtaining said custom formdata; receiving said field data from said fields as input; storing saidfield data in said at least one of said plurality of properties; andtransmitting said item to a recipient.
 54. The computer-readable mediumrecited in claim 53, wherein said step of obtaining said custom formdata comprises the steps of: displaying a form; altering said form inresponse to input; and creating said custom form data corresponding tosaid altered form.
 55. A computer-readable medium on which is stored acomputer program for displaying an item in the context of a form, saidcomputer program comprising instructions which, when executed by acomputer, perform the steps of: receiving said item, said item includinga plurality of properties; determining whether said item includes a formproperty; in response to a determination that said item includes saidform property, retrieving form data stored in said form property;otherwise, retrieving form data from a form registry; and displayingsaid item in the context of a form, said form being defined by said formdata.
 56. The computer-readable medium of claim 55, wherein said formdata defines the layout of a plurality of fields of said form, andwherein information is displayed in said fields, said information beingstored in at least one of said plurality of properties.
 57. Thecomputer-readable medium of claim 55, wherein said form registrycomprises data stored on a memory storage device, said datacorresponding to a description of at least one form.
 58. Thecomputer-readable medium of claim 55, wherein said form propertycomprises data corresponding to a description of said form.
 59. In animproved item for transmission in an electronic mail system, said itemincluding a plurality of properties, the improvement comprising: formdata stored in a form property, said form data defining a custom formused to display said item.
 60. In an electronic mail system fortransmitting a message item, a method for sending to a plurality ofrecipients a message item and automatically tallying responses of saidplurality of recipients to said message item, comprising the steps of:creating said message item, said message item including a query and aplurality of predefined responses; transmitting said message item tosaid plurality of recipients; receiving a reply message item from atleast one of said recipients, said reply message item including replydata corresponding to one of said predefined responses; and tallyingsaid response corresponding to said reply data included in said replymessage item.
 61. The method of claim 60, wherein said step of creatingsaid message item, comprises the steps of: adding an autoresponseproperty to said message item; receiving response data corresponding tosaid plurality of predefined responses entered by the sender of saidmessage item; and storing said response data in said autoresponseproperty.
 62. The method of claim 60, wherein said message item furtherincludes a plurality of voter properties, each of said voter propertiescorresponding to one of said plurality of recipients.
 63. The method ofclaim 60, wherein said reply message item further includes a replyproperty and a message identification property, said reply propertyincluding said reply data stored in said reply property, said messageidentification property including identification data stored in saidmessage identification property, said identification data identifying asent mail copy of said message item, and wherein tallying said responsecomprises the steps of: reading said identification data; locating saidsent mail copy of said message item based on said identification data;locating a voter property in said sent mail copy of said message item inresponse to locating said sent mail copy, said voter propertycorresponding to said at least one of said recipients; and storing saidreply data in said voter property.
 64. The method of claim 60, whereinsaid step of tallying said response occurs automatically at predefinedtimes without any intervention from the sender of said message item. 65.The method of claim 63, further comprising the steps of: calculatingvoting results for each predefined response, said voting results equalto the number of recipients who selected each of said plurality ofpredefined responses; and displaying said voting results to said senderof said message item in response to input from said sender.
 66. Themethod of claim 65, wherein said step of displaying said voting resultsfurther comprises the steps of: displaying a name corresponding to eachof said recipients, and displaying said predefined response selected byeach said recipient.
 67. In an electronic mail system for transmittingand receiving message items, a method for selecting one of a pluralityof predefined responses in reply to a message item that includes aquery, comprising the steps of: opening said message item, said messageitem including response data corresponding to said plurality ofpredefined responses, displaying a plurality of voting buttons, eachsaid voting button corresponding to one of said predefined responses;receiving input corresponding to the selection of one of said votingbuttons; creating a reply message item, said reply message itemincluding a plurality of properties; and storing reply data in at leastone of said plurality of properties, said reply data corresponding tosaid selected one of said voting buttons.
 68. The method of claim 67,wherein said step of storing reply data comprises the step of storingsaid reply data in a vote property of said reply message item, such thatsaid message item may be updated by storing said reply data from saidvote property in a voter property in said message item.
 69. The methodof claim 67, wherein said step of storing reply data comprises the stepof storing said reply data in a subject property of said reply messageitem, such that said reply data will be displayed in the subject fieldof said reply message item.
 70. A computer-readable medium on which isstored a computer program for selecting one of a plurality of predefinedresponses in reply to a message item that includes a query, saidcomputer program comprising instructions which, when executed by said acomputer, perform the steps of: opening said message item, said messageitem including response data corresponding to said plurality ofpredefined responses, displaying a plurality of voting buttons, eachsaid voting button corresponding to one of said predefined responses;receiving input corresponding to the selection of one of said votingbuttons; creating a reply message item, said reply message itemincluding a plurality of properties; and storing reply data in at leastone of said plurality of properties, said reply data corresponding tosaid selected one of said voting buttons.
 71. The computer-readablemedium as recited in claim 70, wherein said step of storing reply datacomprises the step of storing said reply data in a vote property of saidreply message item, such that said message item may be updated bystoring said reply data from said vote property in a voter property insaid message item.
 72. The computer-readable medium as recited in claim70, wherein said step of storing reply data comprises the step ofstoring said reply data in a subject property of said reply messageitem, such that said reply data will be displayed in the subject fieldof said reply message item.
 73. A computer readable medium on which isstored a computer program for sending to a plurality of recipients amessage item and automatically tallying responses of said plurality ofrecipients to said message item, said computer program comprisinginstructions which, when executed by said a computer, perform the stepsof: creating said message item, said message item including a query anda plurality of predefined responses; transmitting said message item tosaid plurality of recipients; receiving a reply message item from atleast one of said recipients, said reply message item including replydata corresponding to one of said predefined responses; and tallyingsaid response corresponding to said reply data included in said replymessage item.
 74. The computer-readable medium as recited in claim 73,wherein said step of creating said message item, comprises the steps of:adding an autoresponse property to said message item; receiving responsedata corresponding to said plurality of predefined responses entered bythe sender of said message item; and storing said response data in saidautoresponse property.
 75. The computer-readable medium as recited inclaim 73, wherein said reply message item further includes a replyproperty and a message identification property, said reply propertyincluding said reply data stored in said reply property, said messageidentification property including identification data stored in saidmessage identification property, said identification data identifying asent mail copy of said message item, and wherein tallying said responsecomprises the steps of: reading said identification data; locating saidsent mail copy of said message item based on said identification data;locating a voter property in said sent mail copy of said message item inresponse to locating said sent mail copy, said voter propertycorresponding to said at least one of said recipients; and storing saidreply data in said voter property.
 76. The computer-readable medium asrecited in claim 73, further comprising the steps of: calculating votingresults for each predefined response, said voting results equal to thenumber of recipients who selected each of said plurality of predefinedresponses; and displaying said voting results to said sender of saidmessage item in response to input from said sender.
 77. Thecomputer-readable medium as recited in claim 76, wherein said step ofdisplaying said voting results further comprises the steps of:displaying a name corresponding to each of said recipients, anddisplaying said predefined response selected by each said recipient. 78.A computer system for sending to a plurality of recipients a messageitem and automatically tallying the responses of said plurality ofrecipients, comprising: a central processing unit (CPU); an input devicecoupled to said CPU for receiving data input by a user; a pixel-baseddisplay device coupled to said CPU for displaying data; and said CPUbeing operative to: create said message item, said message itemincluding a query and a plurality of predefined responses; transmit saidmessage item to said plurality of recipients; receive a reply messageitem from one of said recipients, said reply message item including areply property and a message identification property, said replyproperty including reply data, said message identification propertyincluding identification data identifying a sent mail copy of saidmessage item; open said reply message item; read said identificationdata in said message identification property; locate said sent mail copyof said message item based on said identification data; locate a voterproperty in said sent mail copy of said message item, said voterproperty corresponding to said one of said recipients; and store saidreply data in said voter property.
 79. In an improved message item fortransmission in an electronic mail system, said message item including aplurality of data properties, the improvement comprising: anautoresponse property including data indicative of a number ofpredefined responses to a query in said message item; a vote propertyincluding reply data indicative of the predefined response selected by arecipient of said message item; and a plurality of voter propertiescorresponding to each of said recipients of said message item, saidvoter properties being used to store reply data received from saidrecipients.